NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN102 will not Acquire and IP and Connect to Network
Here is the situation. I have a ReadyNAS 102 version 6.10.2 connected to a Netgear 16 port Gbit switch which is then connected to my Netgear WNR3500 wireless Router which provided the assigned IP...
Maestro64 wrote:
However, If the NAS is not direct connect to the router it will not show up on the network. Using all the same cables as connected to router, and then reconnecting to the switch the network lights on the ENET port only blinks a couple of time and stop and will not connect to the network. When connected to router the network light blink like normal and continue to blink so the network adapter in the NAS is fine.
The next troubleshooting steps are to
(a) try switching the NAS to a different switch port
(b) try connecting router to the the switch using a different switch port.
(c) try using different ethernet cabling.
Are the other devices on the switch behaving normally? What model switch are you using?
StephenB wrote:The next troubleshooting steps are to
(a) try switching the NAS to a different switch port - Already tried same result
(b) try connecting router to the the switch using a different switch port. - Already tried, same result
(c) try using different ethernet cabling. - Already tried, same result
Are the other devices on the switch behaving normally? - Yes all other devices are working fine once I cleared the IP conflict issue since all devices are not using the routers DHCP service to get their IP, no MAC address reseversation.
What model switch are you using? - I will have to look later, however, I am 99% certaint this is not the issue at this point since it works for everything else I plugged into it.
At one point I was thinking the ENET port on the NAS went bad, until I plugged NAS into the router and it used the originally MAC address reservation IP (192.168.1.10) and showed up on the network, it keep reusing this IP address and I knew this would be problematic since the rounter is only using DHCP and the NAS turns on and off each day. I finally the NAS will put a new IP address when it turns on when directly to the router but when the switch is between the router and NAS the it fails to acquire an IP address and self assigns.
Did you also set a static IP in the NAS? If so, it may now be conflicting with another device since it's not reserved.
Sandshark wrote:Did you also set a static IP in the NAS? If so, it may now be conflicting with another device since it's not reserved.
The NAS IP is set to DHCP, along with all the hardwire devices, I used the router to set the IP address. I ran into the IP conflict issue in the past when I set each hardware device to a static IP and the decieve was not connect or turned on at the time when other devices connected. The router was originally set to have all MAC address reservation set between xxx.xxx.1.2 and xxx.xxx.1.99 and the DHCP server was set to xxx.xxx.1.100 to xxx.xxx.1.255. This originally ensured the DHCP address never crossed over to the static IP addresses.
Maestro64 wrote:
What model switch are you using? - I will have to look later, however, I am 99% certain this is not the issue at this point since it works for everything else I plugged into it.
I get that, but the NAS does work correctly when directly connected to the router. So the router is part of the puzzle.
One more thing you could try - after DHCP fails, remove the ethernet cable to the ReadyNAS and reinsert it. Then see if DHCP is successful.
Another option (if practical) is to just leave the NAS connected to a router LAN port.
Once your NAS is connected directly via the router, can you reserve an address for it and then move it to the switch? As a temporary measure, try setting the NAS to a staic IP with that address, too.
I do have two damaged DuoV2's that work fine with some switches/routers and not others. In particular, they don't work right with "green" switches. I bought them for parts, and they appear to have been damaged by a (probably lightning induced) power surge. One does not communicate at all on some devices, the other only does so at 10 meg. The one that works not at all on green switches works up to 100M on some "full powered" devices, and the one that can get 10M on green switches works flawlessly on some.
There are some things about your situation that sound a bit different than this, but I wanted to add it just as another thought trail.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
