Vista Tutorial - Can't copy large files from XP Share

I have the same problem when copying from an XP Share on a workgroup.

I can't copy from an XP share to a Vista SP1 laptop ...actually two
different laptops. The limit seems to be 20 Meg for a wireless and
around 100 Meg for a wired connection, almost as if there is a 'time
out' on the copying time. The limit is reached whether it is one file
or many files. When the limit is reached, any files below the limit
will copy correctly. After the limit is reached, the 'Retry' window
will popup. If 'Retry' is pressed, it will copy another limit's worth
of files.

The source XP system is in a windows Workgroup, XP Professional SP2
with the LinkLayer update for Vista added. I took the same laptop to work

and it worked fine on a Domain PC with an XP share folder.


The destination system is a brand new Vista Home Premium with SP1
preinstalled. The network adapters were updated with the latest
drivers.


When the firewalls and all AntiVirus are disabled, the problem still
occurs.
The windows accounts and password match on both systems.
Sharing is turned on and Everyone has read permissions.


On both Vista, file sharing on or off makes no difference
Also, password protection on or off makes no difference.
The transfer quota is set to unlimited.
Windows firewalls are turned off.
The router is a D-Link DIR -655.
When attempting a wired copy, the wireless is disabled.


XP to XP copies work fine. And from Vista to XP works fine (opposite
direction), as does Vista to Vista. It only fails from XP to Vista.


Any help would be appreciated. Cross posted to
microsoft.public.windows.vista.general.
Also as a response to mzfl on 6/21.

I have an open incident with Microsoft, but so far, they have not been able
to resolve the situation.

I highly suspect the new file copy algorithm / permission validation in the
new SP1. SP1 was supposed to correct the file copy problems, but I don't
think it did for some OS installs.


Thanks in advance
-R




"mzfl" <mzfl@xxxxxx> wrote in message
news:75847343-2B56-4AA9-991C-EC6854AE1A58@xxxxxx

For troubleshooting, try to disable auto tuning. If that doesn't work, test
MTU size. These links may help
Vista file transfer issue
Vista file transfer issue. Can't copy large files between Vista and
Windows 2003 · Not Able to READ or Write to External Hard Drive Thru Network
....
www.chicagotech.net/vista/vistafiles.htm

How to determine the optimal MTU
In a case you may need to modify the MTU size and wonder how to
determine the optimal MTU for your system. You can use ping command to do
so, for example, ...
www.howtonetworking.com/VPN/mtu4.htm



--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"newsgroups.comcast.net" <R@xxxxxx> wrote in message
news:w-CdnXscReXknfjVnZ2dnUVZ_qninZ2d@xxxxxx

Thanks J!

I tried the 106167 fix, but no change. Then I tried the net config change
on both systems, but that made no change either.
Which PC was it supposed to be on, XP or Vista?

I'll try the tcpip.sys mod tonight and let you know. Microsoft themselves
haven't tried either of those two options.

Is the tcpip.sys mod on the XP (source) or Vista (destination)?

Thanks,
R


"Jay Moore" <dewdude@xxxxxx> wrote in message
news:942A3211-D06A-4344-A6C8-3A9214EB51CA@xxxxxx

Microsoft has had this problem with Vista since the beginning and, if I read
these posts correctly, even in XP, yet it appears the only definitive
solution is a hacked version of tcpip.sys provided by a non-MSFT genius
developer which is now rejected as foreign by Vista.

Not to be thwarted by such corporate recalcitrance in the face of superior
intellect, the guy has actually implemented a workaround which runs as a
service and dynamically fixes Microsoft's problem on the fly. Moreover, he is
widely expected to repeat the effort with a patch for SP1 shortly - out of
the goodness of his heart, for thousands (if not millions) of anxious
Microsoft customers.

Couldn't MSFT hire this guy, or at least steal his fix?

Add this problem to the standard Vista networking configuration which
implements a throughput control protocol unsupported by 99% of the devices
out there (which results in LAN throughput approaching dial-up speed, and for
which there is a MSFT-published REGISTRY HACK workaround) and you have a
network stack effectively crippled not by techinical incompetence, but by
organizational dysfunction.

Can't anyone write requirements anymore? How about these two: "The product
must be compatible with the previous version, 90% of existing consumer
networking devices, and should be backwards compatible with as many previous
versions of the product as reasonably possible. All meaningful settings
should be user-configurable through the UI."

Backward-compatibility may be difficult, but it is a cornerstone of
Microsoft's success, and was a long-standing Gates edict.

Vista appears to be Ballmer's baby. Spawn of the devil...

I miss Bill already.

"VISTA: The last Microsoft OS you'll ever need!"

"Robert L. (MS-MVP)" wrote: