Force mapped drive not to connect at startup on Windows XP

  • Thread starter Thread starter ryanmhuc
  • Start date Start date
R

ryanmhuc

I have a mapped drive on my laptop which can only be used when i am
connected to a VPN. On logging in it attempts to logon or connect to
the mapped drive and the login hangs for upto 60 additional seconds.
Is it possible to force the mapped drive not to logon until i actually
attempt to use the mapped drive? This way i can have a fast login?
 
I have a mapped drive on my laptop which can only be used when i am
connected to a VPN. On logging in it attempts to logon or connect to
the mapped drive and the login hangs for upto 60 additional seconds.
Is it possible to force the mapped drive not to logon until i actually
attempt to use the mapped drive? This way i can have a fast login?

I'd get rid of the persistent mapped drive in Windows, and create a batch
file login script to launch when you want to use the VPN connection.

net use x: \\server\share /persistent:no

....should be simple enough. You could also begin with

net use * /del /yes
 
"Lanwench [MVP - Exchange]"
I'd get rid of the persistent mapped drive in Windows, and create a batch
file login script to launch when you want to use the VPN connection.

net use x: \\server\share /persistent:no

...should be simple enough. You could also begin with

net use * /del /yes

And be aware that if you've mapped a network LPTx port that
will get deleted too...
 
V Green said:
"Lanwench [MVP - Exchange]"
I'd get rid of the persistent mapped drive in Windows, and create a
batch file login script to launch when you want to use the VPN
connection.

net use x: \\server\share /persistent:no

...should be simple enough. You could also begin with

net use * /del /yes

And be aware that if you've mapped a network LPTx port that
will get deleted too...

Yes, this is true. It's also a pretty rare situation to encounter nowadays,
but thanks for mentioning it.

Login scripts should do all mapping, in my opinion.
 
"Lanwench [MVP - Exchange]"
V Green said:
"Lanwench [MVP - Exchange]"
(e-mail address removed) wrote:
I have a mapped drive on my laptop which can only be used when i am
connected to a VPN. On logging in it attempts to logon or connect to
the mapped drive and the login hangs for upto 60 additional seconds.
Is it possible to force the mapped drive not to logon until i
actually attempt to use the mapped drive? This way i can have a
fast login?

I'd get rid of the persistent mapped drive in Windows, and create a
batch file login script to launch when you want to use the VPN
connection.

net use x: \\server\share /persistent:no

...should be simple enough. You could also begin with

net use * /del /yes

And be aware that if you've mapped a network LPTx port that
will get deleted too...

Yes, this is true. It's also a pretty rare situation to encounter nowadays,
but thanks for mentioning it.

Login scripts should do all mapping, in my opinion.

Yeah, there didn't used to be much of it, but there's been a
resurgence lately as a solution to Vista's problems printing
over networks...

(this is an XP group, but anyway...)
 
Back
Top