Drive mapping reconnect issue

[DancingGeek]

Greetings,

I am seeing an issue with drive mappings as follows:

The user logs on to W2K; sees the message "applying personal settings", then there is a message -

Restoring network connections
Restoring the connection to \\[path]
[cancel is the only option]

Second message -

Enter network password (trying to map to the drive)
Password is not accepted (current or old network passwords have been attempted)

Third message -

Incorrect password or unknown username for [path]
[ok or cancel]

Cancel, then fourth message -

Restoring network connections
An error occurred while reconnecting p: to [path]
Microsoft windows network: no password supplied
[option to not attempt to restore connection; error continues whether this option is selected or not]

All this happens before the logon script is ever started.

Any ideas of where to look for this are greatly appreciated. We have deleted the references to the mapping in the registry, and that @#$ drive keeps coming up...not sure if an application is causing it, or possibly an old user profile related to the previous NT domain (now on Active Directory). Any articles on what exactly is happening with regard to drive mapping in the boot process...anything at all would be helpful....I'm lost.

Thanks in advance for any ideas!

Cheers--
Sheri

 

[DanD76]

Maybe you've done this already but have you tried mapping the problem drive letter to a valid network path and checking the box to Reconnect at logon? Reboot to see if the error has gone. Then, if desired, Disconnect the network drive.

 

[1101001100110101]

dunno if this will fix the issue but have your tried putting in the login script

NET USE [driveletter:] /DELETE this will delete the mapped drive on startup

 

[DancingGeek]

Thanks for the input. The drive letter is actually mapped to a valid network path, and I have also tried disconnecting the drive and rebooting. It still keeps popping up.

I'm not sure altering the login script will help because all this happens before it hits the logon script. The script actually has that drive mapping in it, so once it reaches that, the drive maps correctly; it's just that before it gets there, it's giving the user errors.

Crazy.

Thanks for the suggestions...any other ideas??

s.

 

[mattjurado]

If you have the /persistent switch in the script, try removing it. Then kill the maps manually at the desktop. Reboot, and try again.

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[DancingGeek]

mattjurado - When you say kill the maps at the desktop, do you mean disconnect them and reboot? I've tried that but it keeps popping up. I've even taken the references out of the registry manually. I'm pretty sure this has nothing to do with the logon script at all as we've tested without even running the logon script and the same errors appear. So I'm not sure changing anything in the logon script will get us closer. It seems to me that some app or user profile or something is getting in there before the logon script is called.

 

[mattjurado]

Got it, I have 3 questions:

Does this happen as a domain admin?

Does this happen if you login as a local user?

If so, login as local administrator, disconnect them and reboot?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[DancingGeek]

Have seen the issue with both domain admins and non-admins.

Yes, it happens if you log on as the local user (in fact the same error comes up no matter who logs on the box and whether it is to the box or the domain).

So far, every effort to disconnect the drive has been unsuccessful. I keep thinking it's hidden in a registry key somewhere weird - it doesn't act like a normal drive mapping.

Our theory so far is that the workstation was on an NT domain with certain user profiles, and that when upgraded to Active Directory, those profiles are still linked somehow and causing the errors. Does that make any sense?

thanks for all the help!
s.

 

[nlm9802]

just a thought.. someone playing a joke and put a batch file in the startup folder?

we had someone do that here.. they mapped their lpt port to a printer 2000 miles away.. so when you print to what you thought was the local printer it came out at an office across the country.

good luck

 

[mattjurado]

I would delete any profiles not needed, either by explorer or using User Profiles...

Right click My Computer, go to properties.

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.