NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN102 Invisible on network after move
Heya, Got this RN102 that's been a tank for years and has already suffered through several moves. This move, when rebuilding my lan, I am unable to get the RN102 registered on the network. T...
emopausal wrote:
Machine A (10.245.95.166) can "see" the nas (10.245.95.110) but cannot access it. As previously stated, all ports (read: protocols) on the nas are closed/inaccessible. There's no firewalls involved; just something fecked on the device.
But your RAIDar screenshot says the NAS IP address is 192.168.1.10 which is not compatible with 10.245.95.x. Where are you seeing the 10.245.95.110 address?
That suggests that your old network was 192.168.1.x, and that you'd assigned the NAS a static address. The most direct way to fix it is to change the router to use the 192.168.1.x address space temporarily, which would then allow you to access the NAS.
You can also try doing an OS reinstall on the NAS - which will reset the NAS to use DHCP and also reset the admin password back to password. It also turns off volume quota (which is on the settings wheel on the volume tab).
And I want to make it clear, that when I say pc (or PC), I'm talking about linux boxes.
Machine A (10.245.95.166) can "see" the nas (10.245.95.110) but cannot access it. As previously stated, all ports (read: protocols) on the nas are closed/inaccessible. There's no firewalls involved; just something fecked on the device.
There's no private subnet. There's just one single LAN hanging off this router, all on cable. I can't make the configuration any simpler yet the Netgear NAS is still autistic. It can't even respond to a simple ping much less an http request.
This just after a Netgear recommended security update bricked my Nighthawk (had to RMA that one) so I'm not exactly a fan atm.
Thanks!
--mike
emopausal wrote:
Machine A (10.245.95.166) can "see" the nas (10.245.95.110) but cannot access it. As previously stated, all ports (read: protocols) on the nas are closed/inaccessible. There's no firewalls involved; just something fecked on the device.
But your RAIDar screenshot says the NAS IP address is 192.168.1.10 which is not compatible with 10.245.95.x. Where are you seeing the 10.245.95.110 address?
That suggests that your old network was 192.168.1.x, and that you'd assigned the NAS a static address. The most direct way to fix it is to change the router to use the 192.168.1.x address space temporarily, which would then allow you to access the NAS.
You can also try doing an OS reinstall on the NAS - which will reset the NAS to use DHCP and also reset the admin password back to password. It also turns off volume quota (which is on the settings wheel on the volume tab).
I finally got the router re-configured for a 192.168.1 subnet.
Once that was done, I was able to see the NAS so you were spot-on - thank you! I was then able to get into the webUI of the NAS and disable the static IP configuration, setting it back to DHCP.
Marked your last answer as accepted/solution - lesson learned for me is that if you're hitting the enter key harder as the sole logic behind trying to make it work this time, it's time to go to bed. ;P
emopausal wrote:
I finally got the router re-configured for a 192.168.1 subnet.
Once that was done, I was able to see the NAS so you were spot-on - thank you! I was then able to get into the webUI of the NAS and disable the static IP configuration, setting it back to DHCP.
Great!
One way to avoid this in the future is to reserve an IP address for the NAS in the router (leaving the NAS using DHCP). Netgear routers call this feature "address reservation"; it is sometimes called "Mac Address Reservation" or "ARP binding". Then if you change subnets or routers, the NAS will remain accessible. Reserving addresses also gives you one management point, so you are less likely to accidentally assign duplicate static addresses.
emopausal wrote:
lesson learned for me is that if you're hitting the enter key harder as the sole logic behind trying to make it work this time, it's time to go to bed.
A lesson I sometimes forget myself :smileyfrustrated:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
