Re: TFTP Recovery not working "connect request failed"

Baldr333 · ‎2020-11-09

So, tried updating my firmware for my router, and it ended up glitching out halfway through. Found threads on using TFTP to reflash an update to the router, and have everything set up right, but every time it goes through it says "connect request failed". Tried with TFTP.ex3 as well, and it just times out over and over. Checked ping between static ip and router and it was fine, entered the TFTP command right at the small window where the server pings in on reboot, using the most recent firmware file for my exact router. Not sure what else to try at this point. Hoping my router isnt toast now.

antinode · ‎2020-11-09

> [...] it ended up glitching out halfway through. [...]

Not a very detailed description of what happened, or what the router
does now.

> [...] Found threads on using TFTP [...]

Thanks for the helpful links.

> [...] have everything set up right, [...]

It's nice that you're happy, and you could be right, but, with no
actual evidence, not everyone will share your confidence.

> [...] Checked ping between static ip and router and it was fine, [...]

Actual "ping" command and its output? Copy+paste is your friend.

> [...] entered the TFTP command [...]

Can't see it. Copy+paste is your friend.

> [...] right at the small window where the server pings in on reboot,
> [...]

"small"? Try varying the timing?

> [...] using the most recent firmware file for my exact router. [...]

Can't see that file name, either, but I'd expect an error like
"connect request failed" to be independent of the file.

Havok970 · ‎2021-04-18

The hardware is a joke, they are clearly purposely bricking devices, and this pedant fanboi is here to make sure to harass you and ensure you never actually get support. If they actually followed standards this wouldn't be nearly such a chore. I have tried several methods as well with zero connectivity. My computer, interface is set to a valid IP on 192.168.1.x on /24 sm and .1 gateway. I followed the one directions that are actually relatively precise, the ones from the Windows directions that instruct to wait until the power LED flashes for ten seconds. I still get zero connectivity on port 69 from the gateway IP of 192.168.1.1. I have tried tftp64 and windows. Windows times out with "connect failed" and tftp64 sits and spins on block 0. I will be putting Wireshark on my PC, but this process is shaping up to be the continuance of their original fraud of bricking their customers hardware through neglect and lack of due diligence, if not just outright fraud.

Havok970 · ‎2021-04-18

Greetings,
Wireshark confirmed my suspicions. For the model above, the router needs to have a solid orange power and a link LED on the Lan port you are plugged into, NOT blinking white power LED despite the windows directions stating otherwise. You still can't ping the gateway, but TFTP WILL go through. To review, you still may need to factory reset the router, but to upgrade FW, it needs to boot NORMALLY. Again, my advice for the long term if at all possible is to use RouterOS or something else that isn't proprietary consumer-grade garbage.

Havok970 · ‎2021-04-18

One last thing:
The router came up with all of its previous settings, so yes, this whole thing is a GIANT boondoggle.

antinode · ‎2021-04-18

> [...] I followed the one directions that are actually relatively
> precise, [...]

Were those directions as precise as your description of where to find
them?

> [...] You still can't ping the gateway, [...]

I still can't see your "ping" command, or its output.

> The router came up with all of its previous settings, so yes, this
> whole thing is a GIANT boondoggle.

I would not expect loading new (or same) firmware to perform a
settings reset. Did _you_ expect that? (Why?)

"boondoggle"? Does your router still not work, or is this some new
meaning for "boondoggle"? And why report it here, instead of in your
own thread?

Context:

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

Havok970 · ‎2021-04-18

You were the one who linked to them, so I agree I was wrong to follow any advice from you. Luckily, I'm a networking professional who can use tools like Wireshark, so I was going to solve it regardless of bad procedures and harassment by what appears to be a pedantic shill. Or maybe he just has no life. Regardless, stay away from all cheap proprietary consumer-grade gear is the advice I must re-iterate, or deal with "gurus"