D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-615 => Topic started by: huntpt on September 08, 2010, 10:16:24 PM

Title: DIR-615 B2, Cannot load stored configuration
Post by: huntpt on September 08, 2010, 10:16:24 PM

I have a newly purchased DIR-615, revision B2, running firmware 2.25.  Using a computer running Windows XP Professional Service Pack 3 and Firefox, I cannot load a stored configuration file.  Instead, I get the following message:

RESTORE FAILED

The device may be too busy to properly receive it right now. Please try the restore again. It is also possible that
you are logged in as a 'user' instead of an 'admin' - only administrators can restore the configuration file. Please
check the system log for any errors.

Please press the button below to continue configuring the router.

----------

I would appreciate any suggestions on how to fix this.

Thanks.

Title: Re: DIR-615 B2, Cannot load stored configuration
Post by: !!!!clarkkent on September 09, 2010, 01:41:26 AM

Was the restoration file generated from the same model and hardware revision?

Title: Re: DIR-615 B2, Cannot load stored configuration
Post by: huntpt on September 09, 2010, 09:16:26 AM

Quote from: !!!!clarkkent on September 09, 2010, 01:41:26 AM

Was the restoration file generated from the same model and hardware revision?

Yes, it was.  In fact, it was generated shortly before on the same device to which I tried to restore it.

Title: Re: DIR-615 B2, Cannot load stored configuration
Post by: huntpt on September 20, 2010, 08:24:38 AM

Here is an update: it appears that the WPA encryption key was the problem.  I had been using an encryption key with 63 random printable ASCII characters generated by Steve Gibson's website (http://www.grc.com/passwords.htm), that looked like this:
&bdM^4_:?9ZE|rYE^K.%]Fm]i$DG0?B&_T4u&!Th"yTf&k-t|{Iyy6]Ir0[t}[/
(Not the actual key.)

When I switched the encryption key to 63 random alphanumeric characters (from the same site), that looks like the following, the problem went away.
0Rqfg4UGubTt9688yyj2Ih5rxJhrz7xvWRlO8989yTZDM3fDrBgnWrysTS8MUkB
(Not the actual key.)

I have not done any testing to see if this is a general rule, but at least in my case, it appears that the characters in the WPA encryption key prevented the router from reloading the stored configuration.