Print

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

[Phils]

I've been at this a long time and neither can I.

It may take some time but eventually (with the help of the folks here) it will get fixed.

[gunrunnerjohn]

How about a test from another machine with a large copy to the NAS?  That should tell you something if it does or doesn't crash.

[Phils]

You know what. I just got home. I'm going to try that now.

[Phils]

You know what. I just got home. I'm going to try that now.

OK. I just finished a 15 minute copy without incident from my netbook although I'm linking to a shared drive on my desktop which has been giving me problems. I am now following up with a copy that will take almost 2 hours. Based on the way it's going so far it looks like it will happen with incident.

It looks like memtest86+ will be the next step after I'm done with this.

[gunrunnerjohn]

I'd probably just fire it up before you go to bed and check the results the next morning. 

[Phils]

According to my dialog box, I have 20 minutes to go and I'll be done. It's been going for over an hour with no hint of a problem. As far as I'm concerned, the problem is the desktop pc or something between the 2. That's where my attention has to shift next.

 

[gunrunnerjohn]

FYI, in case you don't have the latest memory test, it was updated recently.

http://www.memtest.org/

[Phils]

The copy completed just fine. Absolutely no problem from my netbook. 35 GB went very well.

My desktop issue will be for Thursday evening.

[gunrunnerjohn]

I have to believe this is something on the specific computer and not the DNS-321.  It could be something as zany as the NIC not able to handle a steady diet of bits, I've actually seen one that would work until you did a sustained transfer.  It didn't bluescreen, but it did stop transferring data and pop up an error.

[Phils]

I have to believe this is something on the specific computer and not the DNS-321.  It could be something as zany as the NIC not able to handle a steady diet of bits, I've actually seen one that would work until you did a sustained transfer.  It didn't bluescreen, but it did stop transferring data and pop up an error.

I just wanted to say that my problem still exists although now that I've done my initial copy the issue is less urgent.

I did run memtest on my pc and after more than 2 hours and 4 standard test passes it did not find any errors. The fact is that on that PC a massive copy to a local, usb, or firewire hard drive doesn't crash like when I transfer the DNS-321. That leads me to conclude that the problemis with the NIC. Someone told me that although my NIC is 10/100, connecting it to a Gb router can be problematic if I use a Cat 5 cable. I've now replaced the cable with a CAT5e so I'll see how that goes.

[gunrunnerjohn]

Well, I'd be TRULY amazed if this is a cable issue.  A bad cable doesn't cause the computer to crash!  I'd suspect the NIC or it's drivers.

[Phils]

I never loaded a driver either but that's the message my BSOD displayed. There wasn't enough info to determine which driver though. My buddy's thought was that it was actually the UPnP driver and that I should check the device manager and if I find a device, I should delete it and let my system find it again.

I seem to have fixed my problem and the above post was not far from what the actual problem was. What I noticed was that my HP Laserjet All-In-One's buttons weren't working. How did I fix it? I unplugged the USB cable and left the printer connected by ethernet cable. When I plugged the USB cable back in, the buttons would freeze again. When I turned off the AV Upnp server in the DNS-321, the buttons would work. There is obviously a problem with the Upnp driver with those 2 devices connected. I don't know if the problem is the D-Link or the HP but they really don't seem to like each other.

So what I have done is leave the printer only connected by ethernet. I just did an Acronis disk image with a file size of 22.0 GB and it worked perfectly for the first time in 3 months.

[gunrunnerjohn]

So, it's drivers, we just don't know which ones?

[Phils]

So, it's drivers, we just don't know which ones?

It seems to me that the Windows Upnp driver that USB depends on must be the same driver or at least a close cousin of the Upnp on the NAS's AV server. It has to be the Upnp driver. My PC is more than 5 years old and although USB has been generally reliable there have been times when USB devices wouldn't connect. I once bought an APC brand 4 port USB hub that would not allow my PC to boot. So the issue is the driver and my PC though - not the NAS.

[gunrunnerjohn]

What Windows UPnP driver are we talking about?