slow response to a mapped network drive

G

Guest

I have a login script that runs and mappes a drive to a folder on a Windows
2003 server. If I open explorer right after logging in, the response to the
mapped drive is very quick. If I do not access the drive for some time, about
an hour, then it takes up to 30 seconds or so to get a response. Once it gets
a response, browsing the drive is very quick and remains quick unless there
is no activity between from my computer to the mapped drive for about an
hour. It will take 30 seconds or so and then it becomes quick again
 
L

LVTravel

Check with your system administrator to see if there is an
inactivity timeout on your connections.

Some installations will allow the server to "unhook" (my
terminology may not be accurate) an inactive connection.
What you are describing certainly sounds like this. When
you frequently access the connection, the "hook" stays
active. After the timeout, you need to reconnect to the
drive which takes the 30 seconds or so.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

mapped network drive keeps disconnecting?? 2
Mapped Network Drive not detected 4
All avaliable network drives are mapped 5
network drive mapping problem 1
Disable cached logins with mapped drives 1
Mapped Drive opens with Search Companion but no files or folders 3
network home folder not mapped correctly 8
Mapped network drive not opening 9

Top