NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bjtjaden
Jul 21, 2019Aspirant
Firmware update failed - router not working now
I attempted to upgrade our Nighthawk R7000P router firmware to version 1.3.1.64 but the upgrade failed. Now the router doesn’t work and the power led light is blinking Amber. What can I do to fix the ...
- Jul 21, 2019
Router now working. My mistake - in the TFTP command I was using 192.168.1.10 instead of 192.1668.1.1. Many thanks to all for your expert assistance!
michaelkenward
Jul 21, 2019Guru - Experienced User
- bjtjadenJul 21, 2019Aspirant
I have tried your solution but when I do the actaul TFTP command - I get the error message: "Timeout occurred - Connect request failed". I can ping 192.168.1.10 successfully but the TFTP command doesn't seem to be working. Any ideas? Many thanks!
- shadowsportsJul 21, 2019Hero
Greetings,
Both antinode and michaelkenward have provided excellent information.
Please post the TFTP command you are running. Please complete with the information applicable to your environment.
tftp -i [router IP] put [firmware filename].[file format].
Besides proper execution, TFTP reflash also depends on timing. There is only an extremely brief window of opportunity after the router has been statrted when the TFTP command must be executed. If you miss this, you have to start over.
To familiarize yourself with this "window" open a command promt and type
>ping [IP Address of Router] -t
then press enter
What you will see...
A continious list of ping requests to the router... they should show fail
Now restart the router, paying attention to the winodw. fail, fail, fail.... reply, reply, reply... fail, fail, fail..
It is during that brief moment (reply) when you must press enter and execute the TFTP command. It might be helpful to have 2 command prompt windows open... having the second one with the command poised to "go" when you press enter.
Let us know if this helps.
- michaelkenwardJul 21, 2019Guru - Experienced User
bjtjaden wrote:
I have tried your solution but when I do the actaul TFTP command - I get the error message: "Timeout occurred - Connect request failed".
Is that the actual error message?
As shadowsports says the exact details are important.
One common issue is that people do not put the firmware that they are trying to write to the router in a directory where TFTP can see it.
In the folder where you are running things like "ping", do a "dir".
dir:
If you don't see the firmware, then it won't work unless you feed the path into the "put" command that shadowsports described.
In other words, the [firmware filename].[file format]
can also include the path to get at the firmware:
[path]\[firmware filename].[file format]
but it is easiest simply to copy the firmware to the folder you are working in.
Windows will usually put you in the current user directory:
C:\Users\[username]>
- bjtjadenJul 21, 2019Aspirant
Router now working. My mistake - in the TFTP command I was using 192.168.1.10 instead of 192.1668.1.1. Many thanks to all for your expert assistance!