morse57
asked on
Disconnected Network Drive problem
Hi folks
I've looked through lots of solutions for this problem and tried several but none seem to have worked.
Setup is a single SBS2003 server with XP Pro SP2 clients
If I run "net use S: \\servername\sharename" from any of our clients, they will all show drive S: correctly in the "My Computer" window.
With the same command in a logon script.bat for client machines, all clients' "My Computer" windows show the share as a "Disconnected Network Drive" immediately on logging on. Double clicking the disconnected drive icon accesses the share correctly without any delay.
I have disabled the timeout on the server & removed old Network folders from all user profiles on the clients' registries, then let them be recreated & populated both to no avail.
Repopulated, the Network\S folder for the DefaultUser shows:
Connectiontype = 1
DeferFlags = 4
Provider: Microsoft Windows Network
ProviderType = 131072
RemotePath = correctly reported
UserName = \networkname\pcname$
Interestingly, the Network folder for CurrentUser is not recreated.
Can you help, please?
I've looked through lots of solutions for this problem and tried several but none seem to have worked.
Setup is a single SBS2003 server with XP Pro SP2 clients
If I run "net use S: \\servername\sharename" from any of our clients, they will all show drive S: correctly in the "My Computer" window.
With the same command in a logon script.bat for client machines, all clients' "My Computer" windows show the share as a "Disconnected Network Drive" immediately on logging on. Double clicking the disconnected drive icon accesses the share correctly without any delay.
I have disabled the timeout on the server & removed old Network folders from all user profiles on the clients' registries, then let them be recreated & populated both to no avail.
Repopulated, the Network\S folder for the DefaultUser shows:
Connectiontype = 1
DeferFlags = 4
Provider: Microsoft Windows Network
ProviderType = 131072
RemotePath = correctly reported
UserName = \networkname\pcname$
Interestingly, the Network folder for CurrentUser is not recreated.
Can you help, please?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SBS_LOGIN_SCRIPT.bat is more easily found under \\servername\netlogon
ASKER
Thanks
OK, working backwards from where I was, I've moved the MapNetworkDrive.bat from the SBS Client Computer\Computer Configuration\Windows Settings\Scripts\Logon setting of Group Policies to the SBS Client Computer\User Configuration\Windows Settings\Scripts\Logon setting, where it works fine.
The question I'm left with is, why does it connect but state it's disconnected for the computer setting in GP and not for the user setting. Sorry but I like to understand these things to avoid future problems.
Cheers
OK, working backwards from where I was, I've moved the MapNetworkDrive.bat from the SBS Client Computer\Computer Configuration\Windows Settings\Scripts\Logon setting of Group Policies to the SBS Client Computer\User Configuration\Windows Settings\Scripts\Logon setting, where it works fine.
The question I'm left with is, why does it connect but state it's disconnected for the computer setting in GP and not for the user setting. Sorry but I like to understand these things to avoid future problems.
Cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great, thanks Jeff.
I've made the change to SBS_LOGIN_SCRIPT.bat & undone the GP changes & it all works fine.
I presume that the "disconnected" problem on the client pc setting is just a quirk of SBS.
One final question before I put up the points, Jeff's script shows persistent = no, whereas suppsaws' version appears to be persistent = yes. Pros & cons of either choice?
Cheers
I've made the change to SBS_LOGIN_SCRIPT.bat & undone the GP changes & it all works fine.
I presume that the "disconnected" problem on the client pc setting is just a quirk of SBS.
One final question before I put up the points, Jeff's script shows persistent = no, whereas suppsaws' version appears to be persistent = yes. Pros & cons of either choice?
Cheers
Its run every time at logon so it maps them each time, if it tires to map them and they are allready mapped some error message is displayed, cant recall what it is off the top of my head.
The reason to use persistent = no is for what Dinga84 describes as well as so that any laptop that is out of the office doesn't try to connect to a non-existent share.
The disconnected problem is due to SBS's running of the login script, which could conflict with the timing of when group policies are applied.
Jeff
TechSoEasy
The disconnected problem is due to SBS's running of the login script, which could conflict with the timing of when group policies are applied.
Jeff
TechSoEasy
ASKER
I see.
Thanks very much
Thanks very much