Environment:
2003 AD, DNS, WINS, DHCP, DC (also Global Catalog), ISA 2004, Exchange
2003, SMS 2003. All traffic in the following example are one hop away @
1 Gb.
XP Pro SP2, user logs in and runs a .vbs (see below) via a GPO to map
two drive shares on the same server, H: and W:. After 30 - 420 minutes
(i know, broad time frame...) of inactivity on the H:
(\\server\username$) the drive becomes disconnected, then _actually_
disappears from My Computer. The "net use" command show no reference to
the share after its lost. Manually mapping H: reconnects the share and
the same pattern would occur over time. There are no problems with
security/share on the folders as the user has Full Control.
2003 Server, turned off the autodisconnect feature via "net config
server /autodisconnect:-1" This problem is not unique to a unique image
but rather company wide. Logs report no user or machine errors in AD
and on the local machine.
Is there something on the file server or workstation that needs to be
enabled\disabled. At this point I am concerned because the same script,
syntax, and \\server are not an issue with the W:
(\\server\share\share)? Or possibly a more descript audit trail?
Thanks...
strUser = "\\server\" & strUser & "$"
WshNetwork.RemoveNetworkDrive "H:", True, True
WshNetwork.MapNetworkDrive "H:", strUser, True
WshNetwork.RemoveNetworkDrive "W:", True, True
WshNetwork.MapNetworkDrive "W:", "\\server\share\share", True
|