Not Mapping Drives in Login script

Has the drive mappings EVER worked on these mahcines?

Actually we just migrated from Novell. But yes they have worked before.

Could you give us the output of a "net use" command of an affected machine, and give use the exact command line you're trying to use in the logon script (I'm assuming you are mapping the drives by logonscript)

Also, there should be some kind of error message when you attempt the drivemapping. That'd be useful too.

The windows 2000 and XP machines are not even running the login script at all. We put the .bat file in the Netlogon folder on our DC and put the name of the .bat file in the users profile. The following is a sample of one of the drive mappings:

IF "%OS%"=="Windows_NT" GOTO NT

:98
If exist Q:\ NET USE Q: /D

NET USE Q: \\server\apps

:NT
If exist Q:\ NET USE Q: /D

NET USE Q: \\server\apps

As i said before windows 98 machines run the script fine. We are even able to map Home drives on windows 2000/XP machines using the users profile in active directory.

Hmmm. If it is only upgraded computers that have this behaviour, check your network properties. I assume you use TCP/IP for network communication, I would suggest disabling other protocols that got left over with the migration and see if that helps. I'm suggesting this because NetBUIE used to do evil things to my network.

Also, check if the computernames do not have spaces in them. That used to cause trouble in the past for macintosh clients for me.

We removed all the IPX and netbuie protocols when we removed the Novell client. And none of our computer names have spaces in them.

After i login to a win2k/XP machine i can double click the .bat file and it maps the share drives fine. i could put the .bat file in the startup menu but i would like to avoid this.

Try keeping your scripts as simple as possible. Create one with just this in it and see if it works.

NET USE Q: /D
NET USE Q: \\server\apps

You don't need all of the extra commands in there because all that junk is saying is that 1.) Delete any map on Q and then 2.) Map Q to this.

TooKoolKris
MCSE+I, CCNA, A+

Understandable you don't want to do that.

Did you upgrade your Domain Controller to 2000 as well recently ? That moves about the folder that is shared as \\server\netlogon. Although I can't imagine why some of your clients would search for the actual (old) folder instead of that share, it is the only explanation I can think of (maybe a leftover from Novell).

TooKoolKris,

I don't think it is the logon script itself that is faulty. Those computers are somehow just not finding the scripts...

Yes, you don't think the .bat files are faulty, but have you actually tried the suggestion? I only takes a second to rename a bat, create a new one and try it...

Try these QArticles:

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q302104


Maybe they're logging on locally?

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q258286

Maybe you need to deny access UNLESS the script runs, just to see what happens...

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q275506

And an article that says DO NOT define command line parameters in logon script(silly, I know):

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q142672

Hope one helps you out...Cheers!

In WinNT, logon scripts are kept in :
   \\<servername>\winnt\system32\repl\export\scripts
   \\<servername>\winnt\system32\repl\import\scripts

In Win2000, my logon scripts are located in :
   \\<servername>\winnt\sysvol\sysvol\<domainname>\scripts

BUT, my server still has the old WinNT directory (which is filled with old scripts - I only discovered them now, hihi). If I'm right and some of your computers are searching another location for the scripts, you should find a solution by copying logon scripts to both locations, and then you're just left to find out how to get all workstations to look for the script in the right location.

Have a jolly nice weekend.

The domain controller has been in place for about a year now cause we were running dual Network OS's. It was not an upgrade but a new DC install.  

We are trying all the suggestions. It seems that we are getting it to pull the login script sometimes but not always.

TooKoolKris method seems to work one time. When i reboot and try it again it doesn't work. Then when we reboot and try ita third time it works.

How many DC's do you have in this domain? It seems that the server is getting banged and can't handle all of the requests. You may need to add another DC like having a BDC in the old NT4 era. Normally something like this either works or it doesn't, so it sounds like congestion or communication problems of some sort.

TooKoolKris
MCSE+I, CCNA, A+

All the comments sound interesting. I faced the same problem 2 days ago. A machine wouldn't map the drives properly on startup but would access the network manually. Changed the network card on the machine. Lo and behold! Drives were being mapped on startup!

Might I suggest a new network card?

I have seen this happen when the default path for the logon script is inaccessible, such as when it is a network drive that doesn't exist.  Try adding C:\ or C: as the first line of your logon script (or whatever the name of your system drive is).

Contact the site moderator and you might be able to get some of your points back.

Yes and thank you for the answer...hehehehheh...