• April 20, 2025, 11:44:21 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Gateway Settings .gws File Corruption  (Read 7663 times)

viperware

  • Guest
Gateway Settings .gws File Corruption
« on: August 30, 2008, 02:28:44 PM »

It seems this problem has been around a long time for people who use a lot of the "Advanced" tab settings in the router. The fact that this has been going on since FW 1.01 and has still not been fixed in the newest version is ludicrous. This is a major programming flaw and should receive top priority attention.
Here is a C/P from elsewhere...
--
Quote
said by scots  :

Has anyone had any issues with restoring their saved configuration after upgrading the firmware? It fails every time when I try to restore my saved configuration. I normally use Firefox so tried it in IE as well just in case, and got the same results. The message I get is:

"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."

I'm logged in as admin, and I have no clue why the device would be "too busy". The same thing happened to me when I upgraded from 1.01 to 1.02, and I ended up entering all my settings manually. Anyone have any ideas?

It's the same f*ckin' sh*t here and I am really f*ckin' pissed as I have a sh*tload of custom settings, almost under every single tab on the advanced page.

WTF is this, Dlink?
WTF IS THIS???

 
to forum · permalink ·  · 2007-05-24 23:11:05
Logged

DVDKingdom

  • Level 1 Member
  • *
  • Posts: 7
Re: Gateway Settings .gws File Corruption
« Reply #1 on: August 30, 2008, 07:13:45 PM »

I got this error today myself.  I just wish there was some valid reason given instead of the generic message.  This way the user could troubleshoot the issue better and maybe resolve.  After all the router should accept the files if they were created by the router correctly in the first place.
Logged

spinn

  • Level 1 Member
  • *
  • Posts: 9
Re: Gateway Settings .gws File Corruption
« Reply #2 on: September 01, 2008, 10:36:36 PM »

Shoot I wish DLink would give us a utility to dump the gws file so we could at least re-enter the configuration data.  Although I agree the corruption issue should be fixed.
Logged

Kittyburgers

  • Level 2 Member
  • **
  • Posts: 68
Re: Gateway Settings .gws File Corruption
« Reply #3 on: October 03, 2008, 10:20:03 AM »

Yes, I was somewhat perplexed by this as well, although I didn't receive the same error message you did.  I received no message.  I thought that the settings were restored, but nothing was restored.  This was upgrading from 1.11 to 1.21.  Something must have gone wrong when saving the configuration file to my drive using IE7.  I keep more than one file on hand (just in case), and I noticed that the one I saved just before flashing the new firmware was only about half the file size, compared to a previous one.  Something must have happened during the save process.  At any rate, I was able to load a previously saved file, which worked.  Thank God there wasn't much difference to the configuration files in the previous saved set-up.

D-Link needs to look into this.
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494
Re: Gateway Settings .gws File Corruption
« Reply #4 on: October 03, 2008, 03:37:10 PM »

Are you sure the transmission wasn't disturbed or something. I've restored alot of different .gws, but never encountered this issue...
Logged
DIR-655 H/W: A2 FW: 1.33

bbell1

  • Guest
Re: Gateway Settings .gws File Corruption
« Reply #5 on: November 28, 2008, 12:41:35 PM »

The root of the problem I encountered ("The device may be too busy...") was that the default address assigned to my host PC after the FW flash was 192.168.0.199 (I think that was it) and that address was reserved for a different MAC address in the saved config file.  There was some note in the log file about the IP address being reserved which tipped me off after a failed config load.

The work around was to assign a different IP address to something not reserved in the saved config file.  I did this by going under SETUP --> Network settings and adjusting the DHCP IP Address Range.  Once I saved and rebooted, the config file loaded successfully.

Hope this helps someone...


Logged