Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gcoxii]

So my nas all of a sudden started losing the network and I am not sure why. Here is a little about my nas:

just a file server for my house
never turns off just humms away on a shelf.
static ip so no issue with duplicate ips
have made no changes since April of 2013
on battery backup with surge protector
newest firmware installed back when it came out.

Things i have tried:
turned it off and on again
made sure there was no other device taking that ip.
reset via the button in the back
changed ip address just incase

More information about the network issue:
Disconnects from network after about 30 minutes
unplug and plugging it back in bring it back to the network for 30 minutes.
tried to access with 2 different computers: win 8 and ubuntu

My thinking is it has worked wonderfully since i got it last year, and now it might just be having a hardware issue .

Many thanks in advance for any help you can offer.

Hugs,
Coxii

[gcoxii]

forgot to add

tried direct connection via network cable (crossover)

[JavaLawyer]

As a general rule, you should avoid using static IP addresses, as conflicts may arise. I recommend setting the DNS-320 and your router to DHCP, and use a reserved IP address managed by the router (rather than a static IP address managed by the DNS-320.

If you have a spare switch laying around, you can test the DNS-320 independent of your LAN by placing the DNS-320 and a PC on the switch and test access.

[ivan]

A couple of questions to try and get a better idea of your network setup.

Has any component been changed on the network around the time the problem first appeared - anything added or changed?

Is the fixed IP of the DNS-320 outside of the DHCP range of the DHCP server? 
For example DHCP range 192.168.0.5 to 192.168.0.52 and the DNS-320 is 192.168.0.60 then you would not have any problems, in fact all our NAS boxes are setup that way.

What does the activity log of the DNS-320 say about  shutting down, does it give a reason, does it even say it is shutting down?

The type of problem you are seeing is usually a network problem and not a NAS hardware problem.  Our DNS-320s have been running 24/7/365 for several years without any problems other than the odd operator problem - usually deleting a file that then has to be restored from the backup box.

The only time I have seen hardware causing a similar problem was when a network card in a PC was going bad, but then it would shut down the whole network and I assume that doesn't happen in your case.

[gcoxii]

A little more info: @ java lawyer i took your advice and put the ip on the nas to dhcp and it still lost network connection after thirty minutes. Tried just a basic switch with both the nas and laptop on dhcp, still 30 minutes and then poof. I tried reserved ips from the router end and set everything on the network to dhcp so that the router could assign ips not me manually putting the ips in, still 30 minutes then poof...gone. my last thing i am going to try to do is manually reset the whole router.

@ ivan:
The fixed ip was 192.168.1.4, my range is 192.168.1.1- .15 so it was in range. There has been a new laptop connected to the network but that was months before the problem started and it has static ip also, (so it can't be taking the ip of the 320).when it first happened it literally happened over night, i had no idea, one minute it was working then the next day it was gone. That night nothing new was added or taken away. i thought it was a fluke so i did a hard powerdown (unplugged and replugged in).After the dns 320 started up again from being unplugged it was on the network for about 30 minutes then went down again. As far as activity logs it is not technically shutting down,it just not on the network, i have to physically shut it down to have it reappear on the network. i can try to put the nas outside of the ip range tonight and let you know what happens tomorrow.

question: if i do a reset on the nas itself will it have to format the drives again when i re-set it up. i have a backup but it is a little rough putting the information back on the drives. It takes a bit.

nother quesation a little off topic: will we ever get glacier support since it is a discontinued product.

[ivan]

First thing, NEVER use a fixed IP address that is inside the DHCP range - that is just asking for trouble.

You could get a copy of SoftPerfect's netscan and see if it will show up anything strange on your network.

Doing a 'reset to default' on your NAS shouldn't touch your disks (at least it hasn't every time we have had to do that) - all it does is to reset all the settings you have made to what they were when you got the unit.  As with all things to do with electronic equipment just remember that Murphy's law applies and have a proven backup just in case.

One of my technicians suggested that you check the fan settings and operation because she had a NAS from another vendor that was having network problems caused by overheating of some of the components.

[gcoxii]

i have set the nas outside of the dchp range and it still loses network connectivity. I thought of the fan also but seems to function correctly (spins up). I have it setup to email me if the temp. gets too hot and it is set on the lowest it can go (149 F) . I set it up on a friends network just to make sure it wasn't my switch and /or router. It did the same thing at his place. attempted the standalone on his switch with just his computer and the nas. and lastly tried direct connection with just the nas and his laptop via cat5. Same results. I think i have ruled out everything but the nas itself. i am going to reset it after making sure my backup is current, which will be hard considering it loses network connection so fast.  other than that i think we can close this thread and move onto a 320L, lol.


edit: I also tried netscan the other day when it first started. nothing else was taking that ip.

[hoppo1]

As a long shot just to test it might be worth changing from static to DHCP just to see if it works or try setting the link speed from auto and forcing 100 or 1000.

[ivan]

gcoxii, your trying the unit on another network and getting the same results proves that the problem resides in the NAS itself.

You should try the 'reset to factory defaults' and see if it does anything but I have my doubts.

It appears to be a hardware problem and those usually require specialist tools to determine and can end up being rather expensive to fix.  We have a policy that if the repairs will cost more than 80% of the replacement cost of a new unit the client has the choice of replacing or repairing with us recommending replacement.  That way we don't get unsatisfied clients.

In your case I assume it is out of warranty - if it is not then see about getting a replacement - so could end up being rather expensive to fix.

Depending on how your disks are setup having a full backup might not be a problem.  RAID 1 and Standard will allow you to take a disk, put it in a USB/SATA caddy or adapter and using your Ubuntu install copy the data from them.  You can't do that with RAID 0 or JBOD.