12-06-2011 03:22 AM
My battered NAS 220 box is hanging in my workshop as a warning customers - I'm not a fan of this slow & badly supported machine.
A friend asked if I'd like another, as he was planning to do the same to his - it had dropped off the network. A factory reset hadn't helped - I offered to investigate - hoping to get a chance to kick the stuffing out of another one of these nasty little boxes.
arp -a showed that the mac address of the NAS had an IP address that was different to his network.
arp -s [IP] [mac address] restored the original (fixed) IP to the NAS 220 and it was now back on the network.
darn - I won't get to jump on that one. But it may help some other Seagate Sufferer.
12-08-2011 10:15 AM
We can certainly understand your frustration, but having more details about the issue would help us troubleshoot the issue.
1. Do you have the most recent firmware installed?
2. Have you tried switching out the ethernet cable?
3. Try directly connecting the NAS to a computer to see if the issue still occurs.
12-08-2011 04:07 PM
Perhaps I didn't make make it clear - the problem is already resolved - the post was to help others who may see a similar problem.
The NAS 220 had changed it's IP address from 192.xxx.xxx.xxx to 169.xxx.xxx.xxx and could not be accessed. Using the arp command as described, I was able to change it back to 192.xxx.xxx.xxx and it all worked again on the network.
1. The firmware is 1231 (long over due for an upgrade!)
2. The owner had replaced the Cat5e cables with Cat6 cables, PC to switch & switch to NAS. It didn't work so he spoke to me about it
3. I used one of the new Cat6 cables to connect PC to NAS - that obviously didn't work either, until I corrected the IP address
But items 2 & 3 are not relevant to this problem. The sad state of firmware 1231 may well be relevant - but I doubt if the long suffering NAS 220 owners will see any improvement there - not even as a Christmas present.
12-13-2011 05:46 AM
Sorry Des_Piser, I hadn't realized it was resolved.