NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Pinkyg
Mar 09, 2017Apprentice
RN214 - No IP address after 6.6.1 Update
Hi Guys, I'm in need of some assistance. I've just updated the rn214 to 6.6.1 and the nas now states no ip address on the front panel. A shutdown has not made any difference. It's directly ...
- Mar 10, 2017
Back up and running!
On my way home I remembered the NAS has a 2nd network port. If it is the settings for the NIC/port that have corrupted during the update, will the 2nd unused port be unaffected?
Swapped the ethernet cable to the other port and got an IP address.
I was then able to reach the network settings on the device.
The problem port was set back to DHCP and the cable swapped back, still no IP address.
A shutdown of the device and it's back up and running on the original port with an IP address.
Set the IP address back to static as before and everything is now back as it was.
Hopefully this can help anyone else who encounters the same problem.
It's possible this issue occurs on devices that apply the update when set with a static IP?
Also thanks to Jak0lantash for your help and suggestions too :-)
jak0lantash
Mar 10, 2017Mentor
You most likely need to run TFTPd64 as admin. Under settings, only leave DHCP Server enabled, configure pool, lease time and defaut gateway, connect your NAS to your PC and see if your PC receives a DHCP request. You can try to reboot the NAS cleanly using the power button (press twice to shut down, press once to start).
Pinkyg
Mar 10, 2017Apprentice
Back up and running!
On my way home I remembered the NAS has a 2nd network port. If it is the settings for the NIC/port that have corrupted during the update, will the 2nd unused port be unaffected?
Swapped the ethernet cable to the other port and got an IP address.
I was then able to reach the network settings on the device.
The problem port was set back to DHCP and the cable swapped back, still no IP address.
A shutdown of the device and it's back up and running on the original port with an IP address.
Set the IP address back to static as before and everything is now back as it was.
Hopefully this can help anyone else who encounters the same problem.
It's possible this issue occurs on devices that apply the update when set with a static IP?
Also thanks to Jak0lantash for your help and suggestions too :-)
- PinkygMar 14, 2017Apprentice
Well after a couple of days operational the NAS has once again decided not to pick up an IP address on one of the ports.
I can connect fine on the second port. THe first port will not connect on either dhcp or static.
Can I roll back to whatever version was before 6.6.1?
- jak0lantashMar 14, 2017Mentor
I don't want to be a pain, but even though I don't work at NETGEAR anymore, I'm pretty sure that this has nothing to do with F/W 6.6.1. That said, you're free to do what you want and roll back to 6.6.0 (which you can find on netgear.com/support).
I'd advise you to clean up your subnet config, and switch everything to DHCP. Don't leave any device on the LAN on static IP, and the router will be able to manage just fine (as long as the pool configured on the router is big enough).
- StephenBMar 14, 2017Guru - Experienced User
jak0lantash wrote:
I'd advise you to clean up your subnet config, and switch everything to DHCP. Don't leave any device on the LAN on static IP, and the router will be able to manage just fine (as long as the pool configured on the router is big enough).
I agree. I'd also reboot your network when you are done (turn all clients off, then reboot the router, then turn them back on).
Related Content
NETGEAR Academy

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