Some insight to a similar situation: see message#
1577856Also, a thread here
http://www.sysprobs.com/windows-7-network-slow, though it may have to do with mixed XP and Win7 computers on the same network. Seems to have helped some (see comments at the end)
>
For example, at one client, sometime overnight between March 12 and March 13 a Trend WFBS update caused Windows 7 computers to no longer be able to connect to a SQL server. XP machines/Terminal Server 2003 sessions still could. The problem was Trend on the SQL Server machine.
>
>Antivirus is so invasive and affects so many facets of computer operation that ruling it out during troubleshooting is pretty much a mandatory first step.>
>Thanks for the example. BTW, here is some more information about performance problems that the client has started experiencing since upgrading to Windows 7:
>
>BUT, if anyone else is using the .exe and has those files open (for example the rubbergrindlog form of the exe), then my SQL performance tests take 2.7 seconds, (almost 10x as long).
>
>As soon as the form is closed on the other machine, then the results go back to 0.2 seconds.
>
>Stated another way;
>
> User 1 experiences this response in rubbergrindlog form User 2 experiences this response in rubbergrindlog form
>User 1 opens form Fast (almost instantaneous)
>User 2 opens form Slow, 3-4 seconds to refresh screen Slow, same as user 1
>User 2 closes form Slow
>User 1 closes form and opens it again Fast
>
>
>Notice that the performance goes slow immediately for both users when user 2 opens the form. User 2 doesn’t have to even enter any data, just have it open. When user 2 closes the form, user 1 doesn’t see an improvement until he also closes the form and restarts it.
>
>If a user runs 2 instances of the exe from his own machine, with both instances running the rubbergrindlog form (and no one else has the form open), it will never show the slow response for the instances of the exe on his machine.
