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

Forum Discussion

DaveCh1's avatar
DaveCh1
Aspirant
Feb 05, 2021

Nighthawk RAX80 LAN ports all dead

I just purchased a RAX80 and got it set up.  The 2.4 and 5G bands are both working, but the LAN ports are completely unresponsive.  No lights or data being transmitted.  I did the firmware update, and I don't see any settings in the app to enable or disable the LAN ports.  I've rebooted several times.

 

Has anyone found a solution for this?

3 Replies

  • > [...] No lights or data being transmitted. [...]

     

       "No lights" anyplace, or no "LAN: 1 2 3 4 5" lights when a known-good
    device is connected to a LAN port with a known-good cable, or what,
    exactly?  What happens if you connect a known-good cable to a pair of
    LAN ports?  To the WAN/Internet port and a LAN port?  What does a
    connected device say about its Ethernet interface when it's connected to
    a LAN port?

     

    > [...] I did the firmware update, [...]

     

       As always, an actual version number would be more useful than your
    opinion of what's "updated" today.

     

    > [...] I don't see any settings in the app to enable or disable the LAN
    > ports. [...]

     

       I'm unaware of any.

     

    > Has anyone found a solution for this?

     

       Warranty replacement?

    • DaveCh1's avatar
      DaveCh1
      Aspirant

      I replaced a similar wifi router with multiple ethernet connections.  The cables and connected devices all work fine on the other router.  When connected to the RAX80, there are no LAN: 1 2 3 4 5 lights, nor are there lights on the devices on the other end of the cable.  The Nighthawk app shows connection to all my 2.4G and 5G devices, but nothing else.

       

      Firmware is V1.0.3.106

      • antinode's avatar
        antinode
        Guru

        > I replaced a similar wifi router [...]

         

           If, in identical situations, router-A works and router-B fails, then
        I'd suspect router-B.  Of course, running those previously suggested
        tests might tend to confirm that conclusion, or not.