Hello,
I have a script which runs a VPN connection , maps a drive and copies a file accross.
It's been running fine for over two years.
However, all of a sudden the script has stopped working when trying to map the network drive....
at this point no x: drive is mapped and the error routine is called due to Err.Number <> 0
However, if we drop down to a command prompt and run the 'net use' command the network drive maps without a problem.
Any ideas why this has started to happen and how we can fix it?
Thanks,
1DMF
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!
I have a script which runs a VPN connection , maps a drive and copies a file accross.
It's been running fine for over two years.
However, all of a sudden the script has stopped working when trying to map the network drive....
Code:
' Update Msg
MsgIE "Mapping network drive, please wait..."
' Map network drive
objNetwork.MapNetworkDrive "x:", "\\servername\foldershare", False, "UserID", "Password"
If Err.Number <> 0 Then
Error_Msg
WScript.Quit
End If
at this point no x: drive is mapped and the error routine is called due to Err.Number <> 0
However, if we drop down to a command prompt and run the 'net use' command the network drive maps without a problem.
Any ideas why this has started to happen and how we can fix it?
Thanks,
1DMF
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!