Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Can't ping ReadyNAS
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-21
05:30 AM
2012-10-21
05:30 AM
Can't ping ReadyNAS
I was messing around with my network today and have run into a strange problem. I was looking through the DHCP table on my router and noticed my ReadyNAS Ultra 4 was not in there so I launched Frontview and checked the IP settings, it was set to get from DHCP server (I assume once it gets this value it sets that as static as when I connect to another router it's displayed as static IP) so I clicked renew IP and it was given the new IP which appeared in the router DHCP table.
Now when trying to ping the hostname or new IP of the ReadyNAS I get 'Request timed out'. The display on the ReadyNAS says the new IP (192.168.1.11) and it appears in the router config with the same IP. RAIDar finds it at the new IP too but if I click the setup button the page could not be displayed, I have tried IE and Chrome. I connected the device to another router and configured the same subnets and made sure the IP is in the DHCP pool and is available. The NAS appears in the new router with the correct IP but the router thinks it is static, the host name is not available on the router so the device is listed as unknown.
I have tried reinstalling the OS but same problem, it is still trying to use the 192.168.1.11 IP.
I have to go out now but will continue to try and fix it when I get back, if anyone has any suggestions then they would be much appreciated!!
Cheers
Now when trying to ping the hostname or new IP of the ReadyNAS I get 'Request timed out'. The display on the ReadyNAS says the new IP (192.168.1.11) and it appears in the router config with the same IP. RAIDar finds it at the new IP too but if I click the setup button the page could not be displayed, I have tried IE and Chrome. I connected the device to another router and configured the same subnets and made sure the IP is in the DHCP pool and is available. The NAS appears in the new router with the correct IP but the router thinks it is static, the host name is not available on the router so the device is listed as unknown.
I have tried reinstalling the OS but same problem, it is still trying to use the 192.168.1.11 IP.
I have to go out now but will continue to try and fix it when I get back, if anyone has any suggestions then they would be much appreciated!!
Cheers
Message 1 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-21
05:35 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-21
06:22 AM
2012-10-21
06:22 AM
Re: Can't ping ReadyNAS
I have rebooted the router and the NAS as well as tried another router.
When I get back home I will try the second LAN port and see how that goes.
When I get back home I will try the second LAN port and see how that goes.
Message 3 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-21
09:06 AM
2012-10-21
09:06 AM
Re: Can't ping ReadyNAS
Okay so I connect the second router to the second LAN port on the ReadyNAS and Raidar then confirms it can be accessed using 192.168.1.11 or 192.168.1.1 (both routers have 192.168.1.254 as the gateway IP) but my PC still cannot connect to either IP or ping it when connected via cable to each router.
Thinking the cache may be the issue I fired up my laptop and connected to the original router over wireless, for some reason straight away I was able to access Frontview so I changed the second LAN IP to fixed 192.168.1.200 (this was not changing the IP I was using to connect) and then my connection started to behave like my PC. I connected the laptop to the second router via cable which restored Frontview access and changed the IP of LAN 1 to a fixed address of 192.168.1.100 and then my PC was able to connect using this IP, but not using the hostname like I always have done before. Rebooting everything seems to have restored access via. hostname so all looking good now. I am intrigued at what could have caused the problem, the log on the NAS didn't report any problems.
Thinking the cache may be the issue I fired up my laptop and connected to the original router over wireless, for some reason straight away I was able to access Frontview so I changed the second LAN IP to fixed 192.168.1.200 (this was not changing the IP I was using to connect) and then my connection started to behave like my PC. I connected the laptop to the second router via cable which restored Frontview access and changed the IP of LAN 1 to a fixed address of 192.168.1.100 and then my PC was able to connect using this IP, but not using the hostname like I always have done before. Rebooting everything seems to have restored access via. hostname so all looking good now. I am intrigued at what could have caused the problem, the log on the NAS didn't report any problems.
Message 4 of 4