Network error

pinniger · 21 Oct 2009

For some reason I am not able to transfer large files to my Windows Home Server (home build). The file will start to transfer then just stop and error out.

The error message says Network Error: There is a problem accessing \\server\folder.

This is on a wired connection so I dont know why it would just be dropping the connection. I can still surf the internet fine during this time.

Realtek RTL8169/8100 network cart, cat5e cable, 10/100 netgear 24 port unmanaged switch, WRT54GL router(tomato firmware). NICs are set to auto negotiate.

Any ideas what could be causing this?

I attached a screen shot of the error message and network monitor.

Iomegaman · 21 Oct 2009

Out of curiosity, rather than "pushing" the file from your computer to yoru server. Log into the server and try pulling the file from your workstation.

This will rule out several things!

Tom

pinniger · 21 Oct 2009

Ok, this is weird. I'm on the server "pulling" the files. It does *almost* the same thing.

It will sit at the "file copy dialog box" that says 5 min remaining for like 7-8 minutes. Then will start transferring for a few seconds, then stop again, the do the same thing over and over. It never gives me an error message though, like when I was on the windows 7 machine.

Another thing to note. I have transferred files fine using my windows xp laptop over a wireless connection. I mean, it took a while, but it was wireless, so i was expecting it.

Also, my WHS backups never fail either, and I believe that is transferring quite a bit of data.

Iomegaman · 21 Oct 2009

Are you running a software firewall on either your WHS machine or your Windows 7 one? If so try temporarily disabling these and see if this makes any difference. It's certainly a strange problem I will give you that!

How big are the files that you are trying to transfer?

Tom

Iomegaman · 21 Oct 2009

Something else to possibly try is to:

- Share the folder containing the file you want to transfer from your Windows 7 machine.

- Mount this share as a drive using WHS (give the share a dedicated drive letter).

- Try transfering the file from this network drive, and if that fails,
- Try to copy the file via the command line.

A little long winded I know but if any of this works, it may help to get a little bit closer to the ultimate solution to your problem.

Tom

pinniger · 21 Oct 2009

The only firewall I'm running is the one with windows 7. Disabling this was the first thing that I tried, didn't help though.

I'm also running Microsoft Security Essentials, I can't find an easy way to disable this, so I guess I'll try uninstalling it.

The windows home server is the default install with the exception of Whiis add-on and 2-1tb external usb 2.0 hard drives added.

I'm try to transfer an audio book. A folder of about 135 mp3s and they are all about 7.5 mb, so nothing to huge

Iomegaman · 21 Oct 2009

I'm by no means an expert at WHS so hopefully somebody else may be willing to advise you further if a problem with this is causing your copying issue.

I'll be interested to hear if MSE makes any difference once you have uninstalled it.

Are all of your network drivers etc up to date. Can't seem to figure this one out - really strange problem!

Tom

pinniger · 21 Oct 2009

ok, I tried copying the files via command line, from my win7 machine(pushing), and after a while it said, "The specified domain is no longer available".

Iomegaman · 21 Oct 2009

I would suggest a DNS error, but then one would think that once a file has started copying accross the network the DNS resolution is completed.

I don't know ANYTHING about Tomato firmware routers but could this be the issue? Try turning it off and on again - and yes, I hate myself for saying that

pinniger · 21 Oct 2009

I had updated all nic drivers, my pc has two nic cards, and I've tried both ports as well. I uninstalled MSE, rebooted my router.

still getting the "The specified domain is no longer available" via command line.

It must be the DNS I guess. I have both the WHS and win7 machine set as static IPs though.