Mapped Shares Not Visible on Windows 7 Client
Posted: Mon Sep 16, 2013 5:14 pm
Good-day,
I'm running into a strange issue on a Windows 7 machine. I'm working on deploying OpenVPN to our mobile workforce and they've requested the ability to have their home drive and another share automatically mapped when they log into the VPN.
So far, I'm using the following lines in a batch file:
The command prompt opens as expected and the script executes successfully, however, I cannot see the network drives listed. If I immediately attempt to run the script manually, I get an error 53 telling me that the name is already in use.
As the image below shows, if I disconnect the VPN tunnel then reconnect without running the script automatically (i.e., by removing the UP script on the config folder), then run the batch file manually, the shares are mapped and they show up.
Image showing successful manual share mapping:
Someone suggested to me that because I'm running the OpenVPN GUI as Administrator, perhaps the UP script is also running in that context - therefore, the mapped drives are being mapped for the user "Administrator" and not the currently logged on user? Is this the case, if so, how do I rectify this issue?
Any assistance would be really appreciated, thanks.
I'm running into a strange issue on a Windows 7 machine. I'm working on deploying OpenVPN to our mobile workforce and they've requested the ability to have their home drive and another share automatically mapped when they log into the VPN.
So far, I'm using the following lines in a batch file:
Code: Select all
net use O: \\172.23.6.127\shares /persistent:no
net use U: \\172.23.6.127\%USERNAME% /persistent:noAs the image below shows, if I disconnect the VPN tunnel then reconnect without running the script automatically (i.e., by removing the UP script on the config folder), then run the batch file manually, the shares are mapped and they show up.
Image showing successful manual share mapping:
Someone suggested to me that because I'm running the OpenVPN GUI as Administrator, perhaps the UP script is also running in that context - therefore, the mapped drives are being mapped for the user "Administrator" and not the currently logged on user? Is this the case, if so, how do I rectify this issue?
Any assistance would be really appreciated, thanks.