Print

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

[clstan]

Ever since I upgraded our DNS-323 from FW: 1.03 to 1.04 (and the following 1.05 firmware), any time I try to access the device's Volume_1  (ie:  \\192.168.0.4\Volume_1) ...it IMMEDIATELY causes a Cold Boot on the desktop I'm accessing it from.  Unfortunately...this problem is NOT on all desktops.  But I have yet to find a pattern to those desktops that ARE crashing.

I CAN however backtrack to FW 1.03 and the problem goes away...but I don't get any of the benefits of 1.04 or 1.05 fixes.

Anyone else have this and what did you do to fix it?

Chris

[fordem]

Nope - in fact this is the first I'm hearing about it and I'm inclined to say the problem lies in the desktop - what OS are you using?  I believe changes were made to SAMBA at the 1.03 -> 1.04 upgrade, so that may be an area to examine.

[ECF]

Odd,  I have not herd anyone else reporting this issue it seem it may be something with your PC.

[clstan]

Both desktops are running XP Pro with latest Updates.
I have a laptop that can access it with no problems...and even other XP Pro desktops that also have no issues.

[ECF]

There are 2 desktops now with this same issue?

[clstan]

It occurs on MULTIPLE desktops.  (Not just 2...sorry if I didn't clarify better.)

[ECF]

Hmm I have never herd of or experience a network device such as this to cause a PC reboot. So just from having the DNS-323 mapped to your PCs when they seem to reboot? Does this happen when accessing data only and what type of data is causing this or is it all? Do you have a program you use on you PC's that store data to the DNS-323 that you are trying to access when this occurs?

[clstan]

If I were to Map a drive to one of the desktops...then as the computer is rebooting and re-establishing the maps...it causes immediate hard boot.  Once I found the cause of the problem...I had to turn OFF the DNS-323 just to get the PCs to fully boot so that I could remove the Map.

Running the command "\\dns323" in the command line will not reboot the desktop.
It's AFTER the new window appears and shows the shares on the DNS-323.
JUST CLICKING on the Volume1 share will cause desktop to reboot.

The PCs do use a backup package at night to store their data to the DNS-323.  That's what got my attention because I stopped getting completion (or failure) emails.  As soon as the backup software tried accessing the DNS-323 (in this case...as a network share "\\dns323\Volume1\Backups"...the desktop would reboot and the backup would never occur.

But I CAN reproduce the issue outside of the backup software...AND the issue DOES occur even on those PCs that do NOT have the backup software installed......so I can (with 99% certainty) exclude the backup software from causing the issues.

Computers will reboot with ANY access to the Volume1 share.

I hope this MaYbE helps.
Chris

[Lycan]

What virus/firewalll software are you running on these machines?

[clstan]

Anti-Virus:  Currently running AVG 8.0.  Was running 7.5 when the issues first started appearing.
Firewall:  Just the one built into Windows.

I don't think that it's the AV software.  Its on all the PCs.  Some have the DNS-323 issues...others don't.

[ECF]

The AV software seems to be the only thing on a PC that could possibility cause a reboot like this and is the larges common denominator of the PC's. The software may have some issue scanning Mapped network drives or this particular one causing the PC to reboot. I would recommend contacting AVG or refer to there website and see if this is a herd of issue with this software and NAS devices.

[clstan]

But what about the machines WITH AVG on them that CAN access the drive with no issues?

[ECF]

I wouldn't know what to say this just seems like the only possibility. This is a very strange issue to see on a PC and to see it on multiple machine I don't know what else it could be. Perhaps somebody else on the forums may have some insight with issue seen using AVG software on there PC.

[sowens01]

He is not the only one having this issue.  2 days ago, my computer started getting fatal errors and rebooting when I tried to access the mapped NAS drive on Win XP Pro w/SP3.  I removed the drives and put them in a linux machine and there are no problems with the drives.

[fordem]

He is not the only one having this issue.  2 days ago, my computer started getting fatal errors and rebooting when I tried to access the mapped NAS drive on Win XP Pro w/SP3.  I removed the drives and put them in a linux machine and there are no problems with the drives.

If you have the drives in the DNS-323 can you access them from the linux system.

The issue here seems to be with the system that is crashing and not the DNS-323