D7000 restore configuration error

[Jack76]

Hello,

I try to restore the .cfg file from a backup created a few minutes before, my D7000 router returns "config check fail" error  on the file. I've tried both with the latest firmware 1.5.0 or with the previous 1.48. Any times i created a new backup file, but the restore returns the same error.

Thanks for the support

Jack

[antinode]

> I try to restore the .cfg file from a backup created a few minutes
> before, my D7000 router returns "config check fail" error  on the file.

   I just tried this on my spare D7000 (still at V1.0.1.48_1.0.1), and
had no such trouble.  It also worked using a newer ".cfg" file from my
primary D7000 (V1.0.1.50_1.0.1).  That's using Firefox (56.0.2) on a Mac
(10.11.6).

   The easiest explanation for a failure to restore would be some kind
of file corruption.  These files include a checksum to allow detection
of such corruption.

   Are you editing the ".cfg" file, or storing it or transferring it
using some kind of network software (ASCII FTP, for example), which
might change its contents?  (I'd guess that even changing the line
endings from LF to CR+LF would be enough to cause the checksum test to
fail.)

   Unfortunately, I haven't tried to restore a deliberately corrupted
".cfg" file, and my spare D7000 is packed away again, so I don't know
what the error message looks like when the problem is a corrupt ".cfg"
file.  And this fellow didn't say:

      https://community.netgear.com/t5/x/x/m-p/1395902

[antinode]

> [...] my spare D7000 is packed away again, [...]

   But, knowing that it'll fail (harmlessly, I hope), I could try a
corrupt file on my primary (V1.0.1.50_1.0.1) unit.  That leads to a
pop-up box:

                         Restore failure !
      [ ] Prevent this page from creating additional dialogs

whatever that means.

   Nothing like "config check fail" there, so your problem would appear
to be different from a bad checksum.  Perhaps your D7000 has forgotten
who/what it really is, and sees its own ".cfg" file as foreign.  If the
router is hopelessly confused, then it may be time to try the usual
panacea, a full ("factory") reset (and reconfiguration).

   If it's that confused, then the chances of it ever accepting your old
".cfg" file would depend on how/where it's confused.  If it's writing
out bad data now, then you may be doomed to a manual reconfiguration.
If it's writing out good data now, but it doesn't know a good ".cfg"
file when it sees one, then it might be happier with your old ".cfg"
file after the reset.  And, if a full reset fails to help, then
reloading the firmware might be worth a try.

[Jack76]

Hi Antinoide,

thank you for your support. Unfortunately, the configuration file I'm trying to load has not been changed in any way, so it might be realistic to reset the router and restart with a manual configuration...

I have to find time and spirit to try...

Thank you See you soon

Jack

[eleced]

Hi,

I have the same issue with V1.0.1.64_1.0.1.

Backup settings, save to Downloads, then restore same config (no edits) = Restore failure! Config Check Fail!

Time to take this modem back to the shop I think ...

[antinode]

> Backup settings, save to Downloads, then restore same config (no
> edits) = Restore failure! Config Check Fail!

   Do you have a Mac or other system with a UNIX-like "cksum" program?
Judging by my saved settings files, these things have a reliable
(CRC-32) checksum:

pro3$ find . -name '*.cfg' -exec cksum -o 3 {} \;
558161692 24875 ./NETGEAR_D7000_2017-07-03.cfg
558161692 24921 ./NETGEAR_D7000_2017-07-04_1.cfg
558161692 24921 ./NETGEAR_D7000_2017-07-04_2.cfg
558161692 24921 ./NETGEAR_D7000_2017-07-04_3.cfg
558161692 25193 ./NETGEAR_D7000_2017-08-02.cfg
558161692 25569 ./NETGEAR_D7000_2017-09-18.cfg
558161692 25643 ./NETGEAR_D7000_2017-10-16.cfg
558161692 25643 ./NETGEAR_D7000_2017-10-20.cfg
558161692 25738 ./NETGEAR_D7000_2017-12-14_1.cfg
558161692 25738 ./NETGEAR_D7000_2017-12-29_1.cfg
558161692 25738 ./NETGEAR_D7000_2017-12-29_2.cfg
558161692 25803 ./NETGEAR_D7000_2018-02-06.cfg
558161692 25803 ./NETGEAR_D7000_2018-02-14.cfg
558161692 25803 ./NETGEAR_D7000_2018-02-19.cfg

   Those three fields are the checksum, the file size in bytes, and the
file name.  I'd guess that if your file checksum is different, then the
file is bad.  If the checksum agrees with mine, then the file might have
some other problem.  Or, the firmware can't tell good settings data from
bad settings data.

[eleced]

Hi,

Just a Win10 system, so should be fine for no file corruption.

Modem now returned to store and credited against a TP-Link Archer VR2800.

Free 24 hour tech support, much better parental control / scheduling abitily ... fingers crossed for reliable operation!

Regards

    Ed

[antinode]

   It may be too late to matter, and I'm too lazy to want to disrupt my
stuff for a more similar test, but, for the record, I did try restoring
a settings file from my primary D7000 (V1.0.1.64_1.0.1) to my spare
D7000 (still at V1.0.1.48_1.0.1), and had no trouble.  I used Safari on
a Mac.

   So your (eleced) problem might have been specific to your device, not
a more general D7000 problem.


> I have the same issue [...]

   In general, it's more helpful to start your own thread for your own
problem, and include a link to any other thread of interest.