I'm trying to transfer files from my windows 7 machine to my self built windows home server (old dell 4550). The WHS is the default install except Whiis add-on is installed. I also installed and uninstalled firefly media server add-on, and added two external usb 2.0 hard drives

When I try to copy files, they will start copying then hang until I get this error "There is a problem accessing \server\folder"

When I try to copy via command line, it will copy 2-3 files then say "the specified network name is no longer available" then copy a few more and repeat. this happens with the copy and xcopy command.

I running a 10/100 netgear 24port switch (unmanaged) and linksys WRT54GL flashed with the tomato firmware. cat5e cables.

I have already tried all the basics I could think of like changing cables ports making sure both NICs are set to auto negotiate. Mapped the share as a drive. updated all drivers. uninstalled and reinstalled drivers.

Any body have any ideas?

  • Can these files be be copied inside the Windows 7 machine? – harrymc Oct 22 '09 at 15:42

It disappeared for my when I disabled "network discovery" on Win7. I noted regular network disconnections of Win7 when it says "connected" or "identifying" repeatedly.

Here's a link (via the Internet Wayback Machine) to Microsoft instructions about how to turn network discovery on and off in Win7.

Plus, just in case that link gets broken, here's a screenshot of what it said on 2012-Sep-08:

screenshot of referenced webpage with instructions


This often indicates a hardware problem with the disk(s) and/or disk controllers (I get this problem with faulty RAID controllers frequently). Check your server's event logs to see if you have any messages to that extent and run some hardware diagnostics on your server.

In response to your comment:
There are usually diagnostics that you can run in your computer's setup (BIOS), check your manual or look on Dell's site for instructions for those. Dell also has a list of tools that you can use to perform diagnostics from within Windows.

  • I checked the event viewer and this message came up a lot "persistent drive letter service failed" What do you recommend for hardware diagnostics? FYI, I'm a programmer, not a network/sys admin :) – clair Oct 22 '09 at 15:30

It might be useful to keep a 'ping' running between the machines when you try this out.
If there is a network path problem, ping will show a glitch,
else, you need to start looking at the server machine hardware.

This will keep running at one probe per second till you stop it.

ping -t server

since this is local network, the 'time' should also remain constant;
a varying response time also implies network trouble


Clair, sounds to me like you are having a hardware failure. More specifically, the HDD in the WHS. I would suggest that you replace that drive ASAP and get your data off of it.


I recently got this error while attempting to access a system using UNC path to the hostname. I found that I could access it via IP address but not hostname. I tested DNS and DNS is working fine.

This Fails:


This Works:


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy