Hello. I'm having problem mapping network share with Vista Business using script run by VPN client. There is no domain in this setup, only file server (win 2003 std) in its own workgroup and few clients that connect to servers file share over vpn tunnel. The clients use Zyxel's Zywall ipsec VPN client to open the tunnel and it is configured to run a script that maps the share from server. The problem is that the script does not work in Vista if run by the VPN client. The script is simple logon.cmd (net use x: \\server\share /user:server\user password). Heres what I have tried: -Adjust the ntlm level with secpol.msc -Set more user rights to share -Disabled UAC -Disabled firewall -Different kind of script (VBS) -add 1. Added EnableLinkedConnections reg value ( http://support.microsoft.com/kb/937624 ) But so far nothing have worked. The drive appears under network location but has big red X over it and showing as disconnected network drive. If I try to access it I get "Logon failure: unknown user name or bad password" announcement. This might not sound like big problem since the share is accessible by running the script manually or mapping the share manually but some users find even that too complicated and difficult to be done everytime VPN tunnel is opened.. Here is view from Vista / network location Here is view from server after the VPN client has run the drive mapping script This is the alternate VBS script I used ' From the book, "Windows XP Cookbook" ' ISBN: 0596007256 ' ------ SCRIPT CONFIGURATION ------ strDrive = "x:" strPath = "\\server\share" strUser = "server\user" strPassword = "password" boolPersistent = false ' True = Persistent ; False = Not Persistent ' ------ END CONFIGURATION --------- set objNetwork = WScript.CreateObject("WScript.Network") objNetwork.MapNetworkDrive strDrive, strPath, boolPersistent, _ strUser, strPassword WScript.Echo "Successfully mapped drive"