Mapped drive - slow response at first

[djhawthorn]

Has anyone experienced an issue where you map a network drive, then attempt to access that drive and you get a very slow response at first (takes at least 20 seconds to display any files/folders)? After that initial delay, you have normal response times, so long as you don't leave it idle for more than (say) 10 minutes.

Leave it for more than 10 minutes, and you'll re-experience the slow response time as if it's trying to reestablish a connection pipe with the remote machine.

Ping response times between the client and server are <1ms.

The clients I believe are XP, server is 2003. Server's firewall is disabled; clients must be too cause I can ping them from the server.

I'm sure I've seen this before, but I can't remember what was the cause (let alone the fix). Thanks!

The dumber they think you are, the more surprised they'll be when you kill them!

 

[bcastner]

XP clients at Service Pack2
Windows 2003 Servers at Service Pack 1

Then see:

http://support.microsoft.com/?kbid=840309

Follow the steps in "More Information":

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q265396

Now do:

http://support.microsoft.com/kb/829700/

And turn off Opportunistic Locking at both client and server:

http://support.microsoft.com/default.aspx?kbid=822219

Next: Some of this behavior can be attributed to Antivirus software scanning. This may or not be configurable.

Finally, some easily made configuration changes that can make a big difference:

. Disable search for remote tasks:
Open up the Registry and go to :
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version/Explorer/RemoteComputer/NameSpace

Under that branch, select the key :

{D6277990-4C6A-11CF-8D87-00AA0060F5BF}

and delete it.

. General settings changes:

http://www.ss64.com/nt/slow_browsing.html