Copying compressed files from Server 2008 R2 network share to XP client via VPN fails
Posted
by
Dejan Janjuševic
on Server Fault
See other posts from Server Fault
or by Dejan Janjuševic
Published on 2012-04-11T18:50:55Z
Indexed on
2012/04/14
23:33 UTC
Read the original article
Hit count: 348
At the first sight the question looks similar to this one.
I have experienced an odd behavior while trying to copy a certain file from Windows Server 2008 R2 network share to Windows XP Professional client via VPN. The VPN was set up using RRAS on the server machine. I will try to provide as much informations as possible in order to make the issue more clear.
When trying to copy the compressed file sized ~2.5 MB (via Explorer or CMD, doesn't matter), the process stalls after some 20%, producing an error message after few seconds:
Cannot copy filename: The specified network name is no longer available.
If i start the command ping -t 192.168.2.1
(where the IP address specified belongs to the server) side by side with the copy command, I can clearly see that the ping command times out for few seconds as the copy process stalls. When this happens all network activities are frozen. After a few seconds, the network recovers, ping continues to run normally, however the copy process stands still before it displays the above error message.
Copying other files (I tried 4-5 files), of which some are larger and some are smaller, succeeds. Seems to me that I can copy all uncompressed files. As soon as I try to copy an archive, the process freezes. Even a 707 KB large archive can't be copied.
I can only reproduce this behavior on 2 machines, both Windows XP Professional, one is w/ SP2 and the other w/ SP3. Other XP clients don't have this problem, neither do Windows 7 clients.
If I connect to the server using Remote Desktop Connection without using VPN from either of these 2 machines (using the same user account), I can copy anything I want normally, even these "problematic" files.
Does anyone have any clue about what could possibly be going on?
© Server Fault or respective owner