Windows 7 can't handle shares on Server 2003?

[Sheridan]

Another day, another bizarre windows 7 problem!

 

On some of our Admin PCs the users have several drive letters mapped to various server shares - all currently pointing to various Server 2003 SP2 servers. Their home drive letter is mapped to the root of their share (also on a 2003 server), ie so their h: drive is mapped to \\server\share

 

All working fine in XP and has been for many years. However Windows 7 comes along, and the mapped drives that are created in the login script work fine. But, the home drive that is mapped by AD (in the profile settings) works but any access to it is incredibly slow. By browsing the drives in explorer the other mapped drives list their contents immediately, but the home drive letter hangs and takes ages to display the contents. In the same way if you Start\Run and enter the server \\server the other servers respond by bringing up their list of visible shares almost immediately but the server with the home drives takes forever. All of the servers are running the same hardware and software.

 

This only happens on the Windows 7 PCs and only for the mapped home drive, so is there a known issue with mapped home drives on a 2003 Server? I haven't found anything and this is a big enough issue to roll back to XP as copying files/browsing/opening is unusable.

[witch]

I have a 2003 server with drives mapped by both login script and AD in the profile settings and I have no problem at all on my Windows 7 machines, and I havent heard of anyone else having an issue -so maybe it is something else? Sorry that isn't very helpful but if I can offer info on how my server is set up, in case there is a subtle difference somewhere, then let me know

[elsiegee40]

I have a 2003 server with drives mapped by both login script and AD in the profile settings and I have no problem at all on my Windows 7 machines, and I havent heard of anyone else having an issue -so maybe it is something else? Sorry that isn't very helpful but if I can offer info on how my server is set up, in case there is a subtle difference somewhere, then let me know

What she said... we have it working without issues too.

[DavidYoung]

We had this issue when we first put Windows 7 in. We fixed it by updating the NIC drivers on the server and turning off any TCP offloading or other advanced features on the NIC. Also use this command:

netsh interface tcp set global autotuninglevel=disabled

to disable autotuning on both the server and clients.

[Sheridan]

Ha ha! Thats done it!

 

All the NIC drivers were up to date (and we'd also tried older drivers) but disabling IPV6, and removing the 'Remote Differential Compression' combined with disabling the Autotuning DavidYoung suggested has made a massive difference!

 

I tested some Windows 7 laptops and they were fine - but the admin PCs were recently upgraded to W7 and therefore fully updated. I suspect an update somewhere has caused this but disabling the autotuning had an immediate effect on reboot!

[chazzy2501]

antivirus treating the share as local or something daft. You probably use the same av on your xp machines but maybe with a slightly different config?

[Sheridan]

Same AV on XP and Win7 machines. One of the machines was showing the problem even before the AV was installed!

[bondbill2k2]

We had this issue when we first put Windows 7 in. We fixed it by updating the NIC drivers on the server and turning off any TCP offloading or other advanced features on the NIC. Also use this command:

netsh interface tcp set global autotuninglevel=disabled

to disable autotuning on both the server and clients.

 

Which features should I disable? Offload recieve TCP Checksum, Offload TCP Segmentation, Offload transmit TCP checksum?

Also should these be disabled on both the server and client NICs?