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

Forum Discussion

ncameron's avatar
ncameron
Aspirant
Mar 31, 2022

ReadyNAS says "No IP Address": I can connect to it, but it cannot connect to Internet

I was having trouble loading Spotty on LMS Web interface due to the outdated standard SSL version on this device.

Following laborious instructions on this Forum I managed to update SSL, and now I can load Spotty, BUT I can't run it - as the ReadyNAS has lost all ability to connect outside the local network.  

I can connect to it locally OK with my PC and run the Admin menu, but t cannot check for updates, cannot run Spotty, can't connect to ReadyCLOUD etc. It says "Cannot Get IP Address", even though it has a local one.

Does anyone gave any idea what's going on? It happened immediately I updated the SSL certificate - could that be the cause?

I'm assuming that I will have to RESET the device, perform a lot of Firmware updates, and live with the old SSL certificate - but Internet access is more important than seeing Spotty on the menu!  

11 Replies

Replies have been turned off for this discussion
  • ...I should add that I have:

    - changed the NIC

    - changed the cable

    - rebooted my Router

    - rebooted the ReadyNAS (several times) 

    • StephenB's avatar
      StephenB
      Guru - Experienced User

      Have you done any troubleshooting with ssh?

       

      Checking the gateway configuration with

      route -n | grep 'UG[ \t]' | awk '{print $2}'

      the subnet mask with 

      ifconfig

       

      and the DNS server IPs with 

      cat /etc/resolv.conf

       

      Then also see if you can ping an external address

      ping 8.8.8.8

      and resolve an external dns name.

      nslookup dns.google.com

       

      • ncameron's avatar
        ncameron
        Aspirant

        OK, this is weird, as they all appear to work:

         

        route -n | grep 'UG[ \t]' | awk '{print $2}'

        gets me the Router IP

         

        ifconfig

         gets me, for the active NIC:

         

        Link encap:Ethernet HWaddr e8:fc:af:e6:aa:f8

        UP BROADCAST MULTICAST MTU:1500 Metric:1

        RX Packets:0 errors:0 dropped:0 overruns:0 frame:0

        TX Packets:0  errors:0 dropped:0 overruns:0  carrier:0

        collisions:0 txqueuelen:1000

        RX bytes:279360009 (266.4 MiB) TX bytes:118453605  (112.9 MiB)

        Interrupt:19 Memory:fe800000-fe820000

         

        cat /etc/resolv.conf

        gets me:

        # Generated by Connections Manager 

        search home

        nameserver 192.168.1.1 [the router]

        nameserver 8.8.8.8

         

        nslookup dns.google.com

         get me 8.8.8.8 and 

        8.8.4.4

         

        That all seems to be good doesn't it?