No drive mapping from my login script

[Kerry P]

I'm running a basic win2000 domain. But some (not all) of
my windows XP machines are not mapping drives through th
login script. The only drive they map is the Home drive.
Anybody got any ideas???

 

[PJB]

I'd verify that on the machines that are failing that the users hav
rights to the share.

*I'm running a basic win2000 domain. But some (not all) of
my windows XP machines are not mapping drives through th
login script. The only drive they map is the Home drive.
Anybody got any ideas???

-
PJ

 

[Kerry P]

All the shares and user rights are correct. The scripts
where working fine until a couple of days ago untill I
lost my print server. After rebuilding it I noticed the
scripts were not working. What confused me was the print
server has nothing to do with the scripts. Basically I
have no idea what happened!

 

[Pegasus \(MVP\)]

I'm running a basic win2000 domain. But some (not all) of
my windows XP machines are not mapping drives through th
login script. The only drive they map is the Home drive.
Anybody got any ideas???

Please supply as much information as you can. For example,
what happens when you open a Command Prompt and type
these commands:

ping SomeServer
net use x: \\SomeServer\SomeShare

 

[Lanwench [MVP - Exchange]]

Please supply as much information as you can. For example,
what happens when you open a Command Prompt and type
these commands:

ping SomeServer
net use x: \\SomeServer\SomeShare.

and also...

browse to \\server\netlogon and try to manually run the script.

 

[Guest]

Manually running the scripts works. I copied the script
to the work station desktop and executed it. All the
correct drives are mapped...now I'm even more confused!

 

[Pegasus \(MVP\)]

Time to move into diagnostic mode. Modify your
logon script like so:
@echo off
ver | find /i "XP" > nul && echo on
net use . . .
net use . . .
ver | find /i "XP" > nul && pause

Now watch the action on one of the problem machines.
You should immediately see why some shares are
mapped and others are not.

You can also turn your most recent observation to your
advantage: Remove the script name from the user's account
profile, and place these lines into c:\documents and settings\
all users\start menu\programs\startup\netlogon.bat:

@echo off
\\YourServer\Netlogon\netlogon.bat

This is not as nice and versatile as specifying the logon
script in your users' accounts but it certainly works.

 

[Kerry P]

Sadly that did very little to help. Again the script
didn't run on login and as a result the shares didn't
map. (Other then the home dir)

I also am unable to put the login script on the start
menu because I'm working at a school and with over 1500
user. I have at least 12 user groups all with there own
profiles and login scripts. Obviously these PC are
accessed by different people and groups all day....I
think I might join a convent and leave the PC world
behind me!!!

 

[Pegasus \(MVP\)]

Your post is a little light on details but I think I can make
out the following:
- You have the noble desire to join a convent. Good for your!
- Your logon script does not run on some WinXP PCs.
- Your home share gets mapped not because of the logon
script but because you have specified it in the account
definition.

Now I don't know why some of your WinXP PCs refuse
to run the domain logon script, and since I have never
experienced the phenomenon I cannot propose a solution.
However, the work-around I suggested in my previous reply
can easily be adapted to a multigroup environment, by
modifying the domain logon script like so:

@echo off
\\SomeServer\NetLogon\ifmember.exe Teachers ||
\\SomeServer\NetLogon\Teachers.bat
\\SomeServer\NetLogon\ifmember.exe Admin || \\SomeServer\NetLogon\Admin.bat
.. . .

In other words: Netlogon.bat determines which group the
current user belongs to, then executes the appropriate
logon batch file. ifmember.exe is included with the Win2000
Resource Kit.

Of course it would be nicer to solve the problem instead
of curing the symptom . . .

 

[Guest]

Thank you very much for your advice. I'll give it ago now.

 

[Lanwench [MVP - Exchange]]

Sadly that did very little to help. Again the script
didn't run on login and as a result the shares didn't
map. (Other then the home dir)

I also am unable to put the login script on the start
menu because I'm working at a school and with over 1500
user. I have at least 12 user groups all with there own
profiles and login scripts. Obviously these PC are
accessed by different people and groups all day....I
think I might join a convent and leave the PC world
behind me!!!

Does Apple make iConvent now, or is this a *nix thing?

 

[Edmunde Lee]

I have seen this behaviour if the workstation doesn't quite know where
it's domain controller is... sometimes happens if the domain member
is getting an IP from a DHCP server that isn't providing proper
information for it to jive with its proper domain (if that makes any
sense)

Check your IP settings, and assure that the client(s) are getting the
proper DNS server for their domain.

Do you see eventID 1000 in your event logs? (Unable to determine
user/computer).