dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
5628
share rss forum feed

JDmailNY

join:2007-12-02
Pearl River, NY

[2K3] Mapping network drives After you VPN into network

Our network enviornment is Windows 2003 active directory.
Currently users who work remotely from home are not getting their network drives mappings on their laptop which is Windows XP professional, as they would normally get when they are in the office network.
1.User logs into their laptop at home
2. Manually loads the vpn client
3. The drive script does not mapp drives

How can I map the drives ???



Jahntassa
What, I can have feathers
Premium
join:2006-04-14
Conway, SC
kudos:4

said by JDmailNY:

3. The drive script does not mapp drives
Start with why the script isn't mapping the drives. Probably something in the event viewer.

lorennerol
Premium
join:2003-10-29
Seattle, WA
reply to JDmailNY

My money says it's a name resolution issue. Try using a test script that replaces the host/NetBIOS name(s) with their IP addresses and see if that works.



brianmcd
Premium
join:2000-09-06
Norristown, PA
reply to JDmailNY

Since the user has already logged onto XP (Local) before establishing the VPN Connection the logon script may not be running. Is there an option in the VPN Software to allow it to start BEFORE the XP OS Logon. This way the user can establish a VPN Connection to your network, have their logon credentials validated by the network, and have the network drives mapped.



Archivis
Your Daddy
Premium
join:2001-11-26
Earth
kudos:19

said by brianmcd:

Since the user has already logged onto XP (Local) before establishing the VPN Connection the logon script may not be running. Is there an option in the VPN Software to allow it to start BEFORE the XP OS Logon. This way the user can establish a VPN Connection to your network, have their logon credentials validated by the network, and have the network drives mapped.
This is the winner right here. Map drive scripts will fail because they run before the VPN connection started.

Your script probably has something like this in it.

net use l: /d 1>nul 2>nul
net use l: \\SERVERNAME\SHARENAME$ /persistent:no

Wipe the share name out, recreate it. This is so the scripts can properly be maintained if something changes.

Servername will not resolve until a VPN connection is established. You can either have the VPN connection software set to run on login or have the login script sitting on the user's desktop to run manually after they establish a connection.
--
'A government big enough to give you everything you want, is strong enough to take everything you have.' -Thomas Jefferson -