Windows Forum

Ask something
Discussion Locked

Logon Script Not Working

0 helpful
6 replies

by blaznt2

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok here is the setup. NT4 Domain and NT4 workstations on dhcp with 3c905b or c network cards, HP PIII all MHz 128mb memory min 256mb max approx 411 PC?s. 1 PDC and 2 off site BDC?s.
Ok here is the problem. On certain computers when anyone logs in for the first time since a reboot 3 of the 4 drive mappings don?t work. If they log off and back on it maps all the drives correctly. This happens in different places on the network. It does not follow the computer if you move it to a different place.If you replace the computer it does not happen. New network drivers have been installed. TCP/IP removed and reinstalled. Well that is all the detail I can think of so what does everyone think?

6 replies

by joseph moore

Sounds like a machine name resolution problem. The NetBIOS name cache is purged when you reboot an NT machine. It then takes a while for the proper entries to be added.
There are a few things you can try. The easiest thing is to change the machine names in the logon script to IP addresses. For example, if machine MYPDC has an IP address of 10.1.1.20 and has a shared folder called SHARED, use this syntax:

NET USE X: \\10.1.1.20\SHARED

That will map drive X to the SHARED folder. So, set all drive mappings to IP addresses. That way, it doesn't matter if the machine can resolve MYPDC to 10.1.1.20. The drive mapping will work.

The other thing you can do is hard-code the IP addresses with the machine names in the LMHOSTS file. Say your NT domain is called MYDOMAIN. You could put this line in the LMHOSTS file on all the user workstations:

10.1.1.20 MYPDC #PRE #DOM:MYDOMAIN

That way, when the user NT box is rebooted, when it comes up the entries in the LMHOSTS file are loaded PRIOR to logging on. So, with this LMHOSTS file entry, the machine would be able to resolve MYPDC to its IP address. You could then leave the logon scripts alone, so they could use the machine name:
NET USE X: \\MYPDC\SHARED

by joseph moore

Basically, do either the first option I listed or the second. Either one will work.

There are negatives to both methods. Some people don't like the IP addresses in logon scripts; if IPs change, the logon script does not work. So, if you change an IP on a machine, you must remember to change it in the logon script.

The same negative applies to LMHOSTS file entries. Change the IP, change the LMHOSTS file on all client workstations. This method also means you have to change the LMHOSTS fileon ALL user systems. That can be a drag!

hope this helps

by blaznt2

We updated the computers to win2000 and that fixed the problem. I did not get to use your suggestions. But they both would have worked from what I know about it.

by aaintesa

Hi

If you are not using LMHOST make sure you have it ticked completely off and tick enable NetBIOS for TCP/IP.

What may be happening is that at first, second logon, it is trying to use the LMHOST to find the PDC, i.e. if this is ticked, then works its way down the Name Resolution List, so eventually, it contacts the appropiate services- WINS or DHS.

by blaznt2

We updated the computers to win2000 and that fixed the problem. I did not get to use your suggestions.

This discussion is closed to new replies.