Mapped Network Drives Problem

[Guest]

Hi

I work for a large organisation mixed Windows Server 2000/XP, PC's mainly
W2K with a few XP pc's. There are 3 Domain Controllers that staff login to
which run login scripts to map network drives depending on the section that a
person works in.

Intermittently, when logging in two network drives will not map - the other
six drives map with no problem . If the user logs off and on again the
drives are restored. This only happens on W2K pc's (with both SP3 and SP4).
This happens in all sections of the building (so not switch related), all
different group membership (so not a particular share) and at any time of the
day.

I've checked error logs and can't see anything obvious.

Any ideas?

Thanks

 

[Pegasus \(MVP\)]

Hi

I work for a large organisation mixed Windows Server 2000/XP, PC's mainly
W2K with a few XP pc's. There are 3 Domain Controllers that staff login to
which run login scripts to map network drives depending on the section that a
person works in.

Intermittently, when logging in two network drives will not map - the other
six drives map with no problem . If the user logs off and on again the
drives are restored. This only happens on W2K pc's (with both SP3 and SP4).
This happens in all sections of the building (so not switch related), all
different group membership (so not a particular share) and at any time of the
day.

I've checked error logs and can't see anything obvious.

Any ideas?

Thanks

Modify your logon script to make it self-logging, then examine the log
files after the problem has occurred.

@echo off
echo %date% %time% %ComputerName% %UserName% %UserDomain% >>
"%temp%\logon.log"
echo %date% %time% %ComputerName% %UserName% %UserDomain% >>
"%temp%\logon.err"
net use s: \\YourServer\Share1 1>>"%temp%\logon.log" 2>>"%temp%\logon.err"
net use t: \\YourServer\Share2 1>>"%temp%\logon.log" 2>>"%temp%\logon.err"

 

[Guest]

Hi Pegasus

Thanks for this. I will try it out and let you know what happens.

Mark

 

[Guest]

Hello Pegasus

Perhaps you are still there?

Anyway, I did what you suggested and was getting an error message as below:

The local device name is already in use.
System error 85 has occurred.

I went back to the login scripts and realised that the logon scripts were
mapping an M:\ drive as the users home drive. This is also set in AD. I
have remmed out the entry in the login script that maps the m:\ drive and
have been testing it further.

Thanks
Mark

 

[Pegasus \(MVP\)]

This is something I could not have guessed. Adding logging
facilities to your logon script made it immediately obvious!