Discussion Locked

Logon script on NT4 Serv not always runs

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

I have several WIn95/98 clients who login to an NT4 Server, and the login.bat script defined in the user manager for domains in the Netlogon share does not always run when logging in. I have noticed that this is usually when doing a logon/logoff with out restarting. Doing a full shut down or restart usually activates the logon.bat when logging on.

Any help appreciated and 150 points to be best answer.. in the meanwhile I will go to some users an manually remap their drives (the ones in the logon script).

10 replies

by curlergirl

Without any details as to the configuration of your network, my first guess would be that you have not replicated your logon scripts to your BDC(s). In order to assure that logon scripts run even when a user is authenticated by a BDC rather than bythe PDC, you need to set up replication from the PDC to all BDC(s). You can, of course, copy of the script(s) manually if you have only one BDC, but this becomes clumsy really quickly. To set up automatic replication, go to Server Manager, then goto the properties of the PDC and click Replication. Specify the BDCs on the export side of the window. Then go to each BDC and do the same thing, specifying the PDC on the import side of the window. On all DCs, you have to make sure that the Directory Replication service is running and logged on with an administrative logon, and that the scripts are initially located in the \%systemroot%\system32\repl\export\scripts directory on the PDC. This will ensure that all scripts are replicated to all domain controllers whenever you make any changes to the scripts located in the Export directory on the PDC. Hope this helps!

by tmaclennan

I have a similar problem, but no definitive answer. However, in my case, it appears that the problem has to do with SMS 1.2 and SQLServer 6.5 on the PDC (no BDC). Whenever I have SQLServer getting too busy, or logging a series of errors, it seems that some users for a period of time lasting 1-3 hours won't get a login script window...timing out is my guess. I would suggest checking your event logs for problems in server applications which might be making the server too busy to answer.

by jason

Do you have more than one Domain Controller other than your PDC?? If so, configure Directory Replication to your BDC's.

by baziite

I think you should try the setting in win98 Client for Microsoft Networks Properties where you choose to restore network connections when you logon . Map a drive to the netlogon share in your Autoexec.bat.

The problem is that when you logoff , the network connection with the netlogon is broken and when you log on again it is not restored because the setting in CMSN allows quick logon which does not restore the connections.When you restart you execute the Autoexec.bat which connects to the netlogon and allows the script to run .

by baziite

Please ignore whatever I said about the Autoexec.bat . If your CMSN properties are set to restore network connections at logon and you are still having the same problem then you can try maping a drive to the netlogon share and use it to execute the logon script in the windows startup file ( you can edit the startup file in the Programs / accesories / system tools / system information folder then tools menu / system configuration utility ).

This discussion is closed to new replies.