Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

logon script doesnt run after logging off and logging back in 98se

Status
Not open for further replies.

lbishop

MIS
Oct 4, 2001
3
CA
Hi there,

I am currently running 1 PDC with 2 BDC's. And have about 300 workstations all running win 98 se. Sometimes when the 98 users log off then go to log back on their logon script doesn't run. I have checked all the obvious like the netlogon directories of the servers and all have the identical scripts in the folder. Also the permissions are identical on the netlogon folders. There are no errors when logging back in it just seems to skip the step of running the logon script sometimes. I have also tried using the policy editor to force authentication and display logon status and both those show up with no errors either. The scripts dont do anything fancy at all they just map drives and set the time. Any ideas?
 
HI!

What is your network configuration (subnets, WAN links, name resolution)?
Are the problematic workstations remote from the PDC?

My guess is this:
Some of the workstations are on branch offices which has a local BDC, and connected to the main office with the PDC by a slow WAN link.
These clients are logging on the BDC, but looking for the login scripts on the PDC, and sometimes time-out this operation because of slow link or name resolution problems.

My advice is to enable "load balancing" using POLEDIT to tell the clients that they should look for login scripts on the authenticating DC and not only on the PDC.
The configuration is in
Default Computer - Windows 98 network - Update - Remote Update:
Configure it to "automatic" mode and check the "load balance" box at the bottom.
Remember to use the 98 version of Poledit and to save the file as CONFIG.POL on the NETLOGON share of the PDC and the BDC's.
This should also be compatible with 95 clients if you have some.

Bye

Yizhar Hurwitz
 
I've had this and it is a known bug - don't know of any fix I'm afraid.
 
All the workstations are on a LAN here in one building. I tried the load balancing idea and it didn't make any difference. I have spoke to some other NT administrators and they too have said they have seen this problem before and were unable to come up with a workaround either.
 
I'm having this too... We've got a Win2k server and 98SE clients. The script is in the right place and when I logon to a client, I get the "windows is executing the login script" pop-up and that's it... No drives mapped or time sync. If anyone can help, I'd really appreciate it.
 
are you using KIXstart? if so, there is a known problem with it and win9x clients not running login scripts properly. solution is to specifically point the location of the kix script to the netlogin share. if not, you will get message "unable to find/access login script" and the script will not run. however, after logoff/login (without reboot) the script will run properly.

jbs
 
HI.

Just some other guesses -

* Look for an LMHOSTS file on the client computer that might have obsolute data.

* Check again WINS and name reolution. Are all clients configured for WINS resolution?

* start Server Manager, and see if there is another BDC listed there which is an obsolute (removed) server.
If so delete it.

Bye

Yizhar Hurwitz
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top