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.
StephenB wrote:
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. - Yeap tried that did not work, however, this gives me an idea to try, which is to use the cable from router to switch and plug into the NAS and have it acquire the IP, then reconnect the NAS to the switch and then the router back to the switch. This is not a permanent solution due the NAS shutting down and retarting each day.
Another option (if practical) is to just leave the NAS connected to a router LAN port. - Currently my router is also my wifi access so it centrally located in the house and the switch and NAS is my network/equipment room in the basement. The router's 4 ports are in use, one of which goes to the switch. I am considering a smaller Gbit switch off the router for the office where the router is but until I understand why the NAS will acquire the IP through the switch it does not make sense.
Maestro64 wrote:
am considering a smaller Gbit switch off the router for the office where the router is but until I understand why the NAS will acquire the IP through the switch it does not make sense.I think you meant "won't acquire". It might not be possible to figure it out, especially if you are using an unmanaged switch.
Another simple test to try - disconnect everything on the switch except the NAS and the router, and see if that behaves normally or not. If that works, try adding back one device at a time, and see if you can isolate the failure to a particular device.
If you want (or need) to take a deeper dive:
The protocol used looks like this:
- A broadcast message is sent by the NAS (DHCPDISCOVER), which the switch should be forwarding to all it's active ports.
- All DHCP servers that receive that message will then allocate an IP address and send that address to the NAS via a second broadcast message ( DHCPOFFER ).
- The client then sends a third broadcast message (DHCPREQUEST). This accepts one of the offers. Since it's broadcast the other servers automatically withdraw their own offers when they see this response.
- The DHCP server whose offer was accepted sends a fourth broadcast message to acknowledge (DHCPACK)
- The NAS should then probe the IP address it receives (with the ARP protocol) to check for a duplicate address.
Since all the DHCP messages are broadcast, you could try to take a wireshark trace from a PC connected to the switch - and see if you can look at this message traffic. You might also try downloading the log zip file, and look at the various logs when the ethernet interface on the NAS is activated. There might be some error messages in there that could give you some clues.
The protocol will clearly fail if the broadcast messages aren't reliably forwarded by the switch. There likely will be some timeout error in the NAS log if that is happening on steps 1-4. The "green" switch issue Sandshark points out could be a factor (and it could be affecting the router's switch port - not the NAS). So that would be one reason why the packets aren't being forwarded or are generating link errors in the switch, but it isn't obvious why this would suddenly start happening.
If you still have some duplicate addresses on the network, step 5 might be failing. That should be logged.
It will also misbehave if you somehow have two DHCP servers on the network - if the one that isn't in the router responds first, then you could end up with a bogus address. An outright failure of the protocol should result in a self-assigned address (169.254.0.1 through 169.254.255.254) - but if you did have two servers, you'd probably see a normal completion with an IP address that might not be compatible with your network (or which might be a duplicate).
Yet another misbehavior occurs if the NAS doesn't realize it needs to send the DHCPDISCOVER in the first place. For instance, if the NAS is connected to a switch, but you disconnect/reconnect the router's switch port. The NAS sees no lost connection, so it has no reason to request a new address. However, if you are booting the NAS, or disconnecting/reconnecting its ethernet cable, it should be sending out the DHCPDISCOVER.
wrote:
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. - Yeap tried that did not work, however, this gives me an idea to try, which is to use the cable from router to switch and plug into the NAS and have it acquire the IP, then reconnect the NAS to the switch and then the router back to the switch. This is not a permanent solution due the NAS shutting down and retarting each day.
Another option (if practical) is to just leave the NAS connected to a router LAN port. - Currently my router is also my wifi access so it centrally located in the house and the switch and NAS is my network/equipment room in the basement. The router's 4 ports are in use, one of which goes to the switch. I am considering a smaller Gbit switch off the router for the office where the router is but until I understand why the NAS will acquire the IP through the switch it does not make sense.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
