• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1980
  • Last Modified:

Windows 7 lag when accessing a file server share

When accessing one particular file server (FS06) from a new Dell Optiplex 980 Windows 7 64 bit computer, there is a 10-12 second lag on opening \\FS06 and each folder thereafter (even if you go back to a folder you’ve already opened).  Accessing other servers on our network is instantaneous.  FS06 and our other servers are in the same location.  The network adapter is the onboard Intel 82578DM.  FS06 is Server 2003 x64.  

If you disable the network connection and then enable it (on the optiplex 980 Win7-x64), browsing shares on FS06 returns to “normal”, until you restart that is, then the problem returns.  

If you install XP on the 980, it works fine.  

All other computer models in our enterprise access FS06 without any problems.  

The Optiplex 960 Win7-x64 had this problem, but it was solved by using an older driver version.  XP did not have this problem on the 960 no matter what driver version.

I have tried every driver version available from Dell and Intel with no luck.  

I tried adding a PCI network card (also Intel) and I had the same problem.

The Optiplex 980 is on the latest BIOS version.

I tried disabling the "Link Layer Topology Discovery" components of the local area connection, no change.

I've tried several 980's, this seems to be a problem with this model, its network driver, or Win 7.

Has anyone else run into this problem.  At this point, this is delaying our Win 7 deployment. We have an unreliable work-around: powershell scripts that disable and enable the network connection in the AM, but it doesn't always run, (scheduling powershell scripts has been fun) and if the user restarts mid day, they run into this problem again.  I'd love a real solution, but i'm thinking its a driver issue and I'm waiting on Dell/Intel to fix the problem...
0
Coilcraft
Asked:
Coilcraft
  • 4
1 Solution
 
fluk3dCommented:
Have you tried accessing the share

\\SERVER
\\FULLFQDN \\SERVER.DOMAIN.LOCAL
\\IP ADDRESS

Please report back
0
 
CoilcraftAuthor Commented:
problem still there weather you use \\fs06,  \\fs06.domain.com,  \\ip-address

also it pings at <1ms
0
 
CoilcraftAuthor Commented:
I've been trying different network cards, all have the same problem.  leading me to believe this is a Win 7 problem

Onboard  Intel 82578DM - every driver version i could find - same problem
Intel pro/1000 GT - latest intel driver - same problem
Netgear GA311 (realtek chipset) - Microsoft driver - same problem
Netgear GA311 (realtek chipset) - llatest Netgear driver - same problem
Netgear GA302T - no Win7 driver - couldn't test
0
 
CoilcraftAuthor Commented:
I tried 3 more PCI gigabyte cards, no luck.  Anyone have any other ideas?
0
 
CoilcraftAuthor Commented:
The Fix:

In an elevated command prompt, type:

netsh interface tcp set global autotuning=disabled

http://www.sysprobs.com/windows-7-network-slow


This article refers to Vista, but I think it’s the same in Win 7

The symptoms exist due to the new re-written TCP stack in Windows Vista that aims to take full advantage of hardware advances such as gigabit networking. Among the new feature in Windows Vista TCP/IP is Receive Window Auto-Tuning Level for TCP connections. TCP AutoTuning enables TCP window scaling by default and automatically tunes the TCP receive window size for each individual connection based on the bandwidth delay product (BDP) and the rate at which the application reads data from the connection, and no longer need to manually change TcpWindowSize registry key value which applies to all connection. Theoretically, with TCP auto-tuning, network connection throughput in Windows Vista should be improved for best performance and efficiency, without registry tweak or hack. However, this is not always the case, and may cause some Internet related issues and problems.
The workaround or solution to the above problem is to disable the TCP/IP AutoTuning in Windows Vista. Disabling auto tuning of TCP Windows Size should not cause any negative effects, only that TCP Window Size will always at default value without ability to optimization to each connection. Anyway, if there is any side effect after turn off auto tuning, simply re-enable back it.

http://www.mydigitallife.info/2007/03/22/disable-tcp-auto-tuning-to-solve-slow-network-cannot-load-web-page-or-download-email-problems-in-vista/
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now