NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN21400 Suddenly Goes Offline but is actually running
My RN21400 with 4 4TB drives has been running flawlessly for many years now. However, I've suddenly lost the ability to keep the NAS online. Although the NAS is running, shares and folders cannot...
I believe that others have found port 2 to do better than port 1. The manual labels the upper port 1 and the lower 2, but the upper is eth1 and the lower is eth0, so there may be some confusion regarding whihc port is best. Of course, that could be because they used port one until it overheated too many times and started to become damaged, then moved to port 2.
On mine, it doesn't seem to matter a lot. But i think my issue is more with 3.3VSB than the NIC.
Two ports can be bonded if you have a router capable of supporting that. Each of the two ports could also be connected to separate networks. If one fails, you don't have a brick since you still have the second to use. And they can also be used to implement OpenVPN using two ports, one of which does not get an IP assigned, which is more efficient than the single port implementation (I did just that before I moved over to ZeroTier since my router didn't support it, though not on a 212).
Here is something odd I just noticed that may or may not be related. I went to see which port I'm currenlty using on it and while the eth0 icon was color and eth1 was greyed out, both showed the same IP address and a 1GB connection. I powered down and switched from the lower to the upper port, and it was normal, eth0 showed an IP of 0.0.0.0 and a connection speed of 0MBPS while eth1 showed the proper IP and 1GB speed. I powered down and went back to using the lower port, and it was back with both showing the IP address and connection speed. It could just be a bug in the GUI, or it may be meaningful.
Through all of this, BTW, it powered on and off just fine.
Checked the temperature of the Server Rack and it runs reasonably cool at 24 degrees Celcius. Perhaps it was the use of both Ethernet ports that caused some overheating and the strange behaviour. I'm now connected to eth0.
A few questions about both of the Ethernet Ports:
1) Is it advisable to use eth1 instead of eth2 to avoid overheating as suggested in this thread?
2) What is the purpose of providing 2 Ethernet ports if the NAS can only take advantage of one or the other at a time? I have 2 ethernet cables connected to each of my NAS's.
If this is answered in another thread, please direct me to it.
The RN214 is running continuously, now up for 46 hours without an issue.
I believe that others have found port 2 to do better than port 1. The manual labels the upper port 1 and the lower 2, but the upper is eth1 and the lower is eth0, so there may be some confusion regarding whihc port is best. Of course, that could be because they used port one until it overheated too many times and started to become damaged, then moved to port 2.
On mine, it doesn't seem to matter a lot. But i think my issue is more with 3.3VSB than the NIC.
Two ports can be bonded if you have a router capable of supporting that. Each of the two ports could also be connected to separate networks. If one fails, you don't have a brick since you still have the second to use. And they can also be used to implement OpenVPN using two ports, one of which does not get an IP assigned, which is more efficient than the single port implementation (I did just that before I moved over to ZeroTier since my router didn't support it, though not on a 212).
Here is something odd I just noticed that may or may not be related. I went to see which port I'm currenlty using on it and while the eth0 icon was color and eth1 was greyed out, both showed the same IP address and a 1GB connection. I powered down and switched from the lower to the upper port, and it was normal, eth0 showed an IP of 0.0.0.0 and a connection speed of 0MBPS while eth1 showed the proper IP and 1GB speed. I powered down and went back to using the lower port, and it was back with both showing the IP address and connection speed. It could just be a bug in the GUI, or it may be meaningful.
Through all of this, BTW, it powered on and off just fine.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
