NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Odd connectivity issues
Hi, I have a Readynas Duo v2 that has been fine for about a year. I don't know if this is coincidence or not but I changed the subnet mask on it on the 2nd Sept and noticed yesterday that I couldn'...
Also seems like a network problem to me, unless there is something with the hard drives.
Do you have spin down set up ? I believe that both interface and share access require disks to spin up whereas ping just need the network card. So it could be a problem with that. It could also be a problem with timeouts while the NAS is under heavy load.
The obvious test would be to take the NAS for a spin on another network, but I believe this is a production machine and that you just can't get it off of the network for a few days. If you could I would suggest using another switch.
Can you isolate conditions where the problem is the most likely to happen ? An hour, a heavy load, something that binds the user (common subnet, common switch, an OS version...)
Can you describe a bit more your network architecture ?
I think you work for enterprise (because of the word staff), this raises a lot of questions for the network environment. For standard folks we usually assume a single wireless router, but here you are speaking of multiple subnets.
So the obvious question is how did you do your subnets ? classic VLan + static routing ? dynamic routing ? is there a firewall, IPS or anti ddos system that could flag the computers ? Do you have QoS ? How did you set the TCP sessions length/timeout ? How are your switch performance, is it overloaded ? Did you enable jumbo frames ?
That's a lot of question, I'm just trying to get the big picture to see what can affect the network connectivity and/or the NAS performance.
Do you have spin down set up ? I believe that both interface and share access require disks to spin up whereas ping just need the network card. So it could be a problem with that. It could also be a problem with timeouts while the NAS is under heavy load.
The obvious test would be to take the NAS for a spin on another network, but I believe this is a production machine and that you just can't get it off of the network for a few days. If you could I would suggest using another switch.
Can you isolate conditions where the problem is the most likely to happen ? An hour, a heavy load, something that binds the user (common subnet, common switch, an OS version...)
Can you describe a bit more your network architecture ?
I think you work for enterprise (because of the word staff), this raises a lot of questions for the network environment. For standard folks we usually assume a single wireless router, but here you are speaking of multiple subnets.
So the obvious question is how did you do your subnets ? classic VLan + static routing ? dynamic routing ? is there a firewall, IPS or anti ddos system that could flag the computers ? Do you have QoS ? How did you set the TCP sessions length/timeout ? How are your switch performance, is it overloaded ? Did you enable jumbo frames ?
That's a lot of question, I'm just trying to get the big picture to see what can affect the network connectivity and/or the NAS performance.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
