NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

snolette's avatar
snolette
Aspirant
Mar 11, 2021

Time Sensitive - Schooling from home - solid orange and no networking

I'm reaching out as I have my son-in-law's router here to try to recover it from a failed firmware update.  I have a solid orange power light and have run through every option including tftp.  I've been in IT for 20 years with networking and haven't had a product I couldn't get back into via a reset.  Nothing is appearing to work.  I do not have it connected to the Internet currently because of my home office.

 

If I have a computer plugged into it, the port indicator is on also, but no IP.  Neither light will blink.  

 

I am unable to access it from any source.  The computer plugged into it cannot locate an IP, or the router, even hardcoded onto the default networks.  My suspicion is that ALL networking is down due to a failed firmware.

 

Without the IP on the router, I cannot work on the firmware issue.  I'm looking for options or whether to tell him to get another router.  Ultimately, I'd like to get this up and on the newest firmware for him.

 

Thank you in advance.

4 Replies

  • plemans's avatar
    plemans
    Guru - Experienced User

    Many things can go wrong with tftp as well as timings can be an issue. sometimes it takes a few tries or different timings while doing it. 

    are you on windows? if so, follow this guide

    https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP

     

    just make sure you enable tftp 

    https://www.thewindowsclub.com/enable-tftp-windows-10

     

    and here's a video walk through using a tftp client. Use the built in one for windows 10 though. the video is more of an example of how its done. 

    https://www.youtube.com/watch?v=R9DLrLQrpaw

     

    and if that doesn't work, you can try using nmrpflash

    https://github.com/jclehner/nmrpflash

    • snolette's avatar
      snolette
      Aspirant

      I am familiar with both, that is not the issue.  The issue is that because the router is not getting to the network stage, I have been unable to connect to it.

      • antinode's avatar
        antinode
        Guru

        > I am familiar with both, that is not the issue. [...]

         

           "both" _what_?  _What_ "is not the issue"?

         

        > [...] The issue is that because the router is not getting to the
        > network stage, I have been unable to connect to it.

         

           I don't know what "the network stage" means to you.  I suspect that
        you might not know as much as you think you do.

         

        > [...] I've been in IT for 20 years with networking [...]

         

           Claims of vast experience or expertise are worth much less here than
        a clear problem report.

         

        > [...] I am unable to access it from any source. [...]

         

           "access it" _how_?  Web browser?  Other?  What, exactly, does "any
        source" mean to you?


           "unable" is not a useful problem description.  It does not say what
        you did.  It does not say what happened when you did it.  As usual,
        showing actual actions (commands) with their actual results (error
        messages, LED indicators, ...) can be more helpful than vague
        descriptions or interpretations.

         

        > [...] The computer plugged into it cannot locate an IP, [...]

         

           Regarding "cannot", see "not a useful problem description [...]",
        above.

         

           What, exactly, does "locate an IP [address?]" mean to you?

         

              https://en.wikipedia.org/wiki/Internet_Protocol

              https://en.wikipedia.org/wiki/IP_address

         

        > [...] or the router, [...]

         

           What, exactly, does "locate [...] the router" mean to you?


        > [...] even hardcoded onto the default networks. [...]

         

           I don't know what any of that means to you.

         

        > [...] My suspicion is that ALL networking is down due to a failed
        > firmware.

         

           Define "ALL networking".

         

        > [...] If I have a computer plugged into it, the port indicator is on
        > also, [...]

         

           That sounds to me like a good (physical) Ethernet connection.  I'd
        count that as "SOME networking".

         

        > [...] Without the IP on the router, [...]

         

           What led you to believe that the _router_ has no IP [address?]?


        > [...] I cannot work on the firmware issue. [...]

         

           I suspect that you're wrong.

         

           If the router's firmware is corrupt, then its DHCP server may not be
        operating, in which case, if your computer is expecting to get its IP
        parameters using DHCP, then that won't happen.  But that, in itself, is
        not fatal.  Or even crippling; only inconvenient.

         

           If you had read the instructions for the TFTP recovery procedure (or
        "nnmrpflash"), then you might have noticed that they include configuring
        the computer's Ethernet interface with static IP parameters, so that it
        _can_ work without access to a working DHCP server.

         

           General advice: Rely less on what you believe that you know, and more
        on what you're told by people whose actual knowledge differs from yours.
        Then describe actual actions and their results, not what you believe to
        be happening behind the scenes, or _why_ you believe that what does
        _not_ happen is not happening.  Or what "the issue" is not.