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

Forum Discussion

vikas027's avatar
vikas027
Aspirant
Apr 21, 2016

Unable to access RN10200 (solved after some issues)

Hello Everyone,

 

I had powered off my NAS for 3-4 days and now when I powered it on, I was unable to access the admin page https://192.168.2.5/admin/ or any share, but the NAS was ping-able.

 

I am ruling out network, laptop/desktop, browser, OS, etc issues since I had tried with different systems and browsers. Even, recycled NAS and plugged/unplugged cables in vain.

 

~$ ping -c 3 192.168.2.5
PING 192.168.2.5 (192.168.2.5): 56 data bytes
64 bytes from 192.168.2.5: icmp_seq=0 ttl=64 time=52.345 ms
64 bytes from 192.168.2.5: icmp_seq=1 ttl=64 time=3.090 ms
64 bytes from 192.168.2.5: icmp_seq=2 ttl=64 time=3.716 ms

--- 192.168.2.5 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.090/19.717/52.345/23.073 ms
~$ nmap 192.168.2.5

Starting Nmap 7.11 ( https://nmap.org ) at 2016-04-21 22:37 AEST
Nmap scan report for 192.168.2.5
Host is up (0.042s latency).
Not shown: 992 closed ports
PORT     STATE SERVICE
80/tcp   open  http
3128/tcp open  squid-http
4443/tcp open  pharos
7676/tcp open  imqbrokerd
8000/tcp open  http-alt
8001/tcp open  vcom-tunnel
8080/tcp open  http-proxy
8443/tcp open  https-alt

Nmap done: 1 IP address (1 host up) scanned in 1.79 seconds
~$

 

I visited http://readycloud.netgear.com and it started updating some firmware after which my NAS was available only under that portal. Then, I got a prompt to upgrade the firmware to v6.4.2 and things started looking good after a reboot.

 

The only issue I had was that SMB service was off after a reboot, which I had to manually enable it.

 

Now, that my issue is resolved after few hiccups, I am just curious to know if this process is normal or could I do something to streamline/avoid this.

 

nmap output after the issue got resolved

~$ nmap 192.168.2.5

Starting Nmap 7.11 ( https://nmap.org ) at 2016-04-21 23:40 AEST
Nmap scan report for 192.168.2.5
Host is up (0.011s latency).
Not shown: 989 closed ports
PORT     STATE SERVICE
21/tcp   open  ftp
80/tcp   open  http
111/tcp  open  rpcbind
139/tcp  open  netbios-ssn
443/tcp  open  https
445/tcp  open  microsoft-ds
548/tcp  open  afp
2049/tcp open  nfs
3128/tcp open  squid-http
8080/tcp open  http-proxy
8200/tcp open  trivnet1

Nmap done: 1 IP address (1 host up) scanned in 0.30 seconds
~$

 

 

 

 

Regards,

Vikas

5 Replies

Replies have been turned off for this discussion
  • BrianL2's avatar
    BrianL2
    NETGEAR Employee Retired

    Hi vikas027,

     

    Welcome to the community!

     

    Thank you for sharing your resolution to the issue that you've encountered. We also appreciate your contribution to the community. 
     
    Though we're not sure what caused this issue on your device, if you could give us a copy of your complete system device logs, we might find something.
     
     
    Kind regards,
     
    BrianL
    NETGEAR Community Team

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More