Network Drives Disconnecting

[mikethomson]

Firtsly, thanks to anyone for help on this, its got me stumped.

A customer I have has various network drives on their desktop. The drive connection is setup through login scripts so sorts it all out during network logon.

Once the logon script has completed ALL the drive mappings show the little red x under the drive until the user connects to them. You can connect to them when you click on them but when you try to run an shortcut where the executable is stored on the network drive it won't run the program saying it can't find the network drive.

This is a weird one, been through loads of different area's within Windows for security etc. I think it is possibly registry but not sure.

Anyone help with this?

 

[BIGALINWALES]

Not sure if this is any good to you but check out this old thread for a similar problem.

thread616-209389

Alex

 

[Guest_imported]

Found the problem.
You may get a red X on drives that are mapped through a logon script if the drive has been mapped previously manually with persistance on.
It seems that when NT remaps the drive before the logon script runs it must lock the drive so that any drive deletions in the logon script don't work, so once the script has completed and you open up explorer the drive appears with a red X.
Go to a command prompt and do a NET USE /PERSISTANT:NO and then go into Windows Explorer and right click on all the drives with red X's and choose Disconnect. Log out and back in again and the logon script will happily map all the drives and they will appear without the X on them.
Worked fine for us so hopefully anyone else with this bizarre problem can use this to fix their issue as well.
Cheers, Tim.

 

[Ntr0P]

If you are like me and have tried everything under the sun, check out this link. I have yet to try it, but it is the only thing that makes sense to me. The last to entries are the ones of interest.

http://www.annoyances.org/exec/forum/win2000/t1016212176