The client machine is running 64 bit Windows 7 and attempting to copy a relatively small file to our NAS device. The NAS device is a Lacie model running (I believe) some variant of Windows XP and has no permission structure aside from access/no access.
Approximately one out of five uploads will be successful. The others will fail at varying times during the upload process and this is visible by the progress bar on the copy dialogue freezing and eventually failing (network location cannot be reached).
So far I haven't been able to isolate the problem. I'm looking for further steps that might help.
Troubleshooting
The NAS is online and has plenty of disk space.
This issue seems to be specific to this one machine. I can't reproduce it on anything else, even when copying to the same network location. The user is authenticated with the same credentials as the rest of the office (low security, general drop box).
I've ruled out a cable or switch problem by reproducing the issue wirelessly on the same machine.
Things to note:
Only uploads to the NAS fail. Downloads work normally and reliably.
The file being transferred does not make a difference though smaller files have a better chance of completing before the connection drops.
Any ideas on how to pin this down?
Best Answer
Hmm, at first it sounded adapter related. But you've tried multiple adapters. That limits server or client issues.
I've similar oddball issues like this before:
Windows 7 and Vista have some TCP autotuning which I've had cause havoc in some smaller client setups when utilizing workgroup connections and some less than stellar network equipment.
To disable TCP autotuning you can run the following from an elevated command prompt:
To disable the system policy (and allow overrides per user level) netsh int tcp set heuristics disabled
To change tuning netsh int tcp set global autotuninglevel=disabled
For more information you can read up on the commands here. I'd recommend starting at disabled and seeing if that helps your problem. If not we are barking up the wrong tree and I'd recommend looking into reseting the TCP stack.