Windows Forum

Ask something
Discussion Locked

Win2K Pro Using a Logon Script from NT?

0 helpful
7 replies

by bejon.parsinia

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

I have a network where I am running a PDC and BDC on NT 4.0 with clients using Win2K Pro. The PDC and BDC contain the needed script files in the correct directories for the users to receive logon scripts. However, these clients intermittently receive all of their mapped drives correctly. Does anyone know of any issues that exist between the two OS' when it comes to using logon scripts???

I know Win2K Pro likes to handle them differently, but why would I be met with only partial success?

Any help is greatly appreciated.

Bejon

7 replies

by qb

Windows 2000 pro doesn't prompt you when it logges you on with cashed credentials. So if the domain controller was momentarily unavailable during login then you users wouldn't get the script. I do remember reading that there is a registry key to add so that you get prompted.

by bejon.parsinia

To be a little more specific, each user is receiving two mapped drives. The intermittent functionality stems from the fact that one drive will map while the other from time to time will not, or neither mapped drive will work.

I am fairly sure that either the PDC or BDC were available as this domain is still in its building stages and I was only using one station to test the scripts. In short, the domain has no active users yet and the servers are not under heavy load.

by ciscofred

I have some more areas that you may look into. Do you have two nics on the pdc and bdc? If so which one is listed in your DNS record? I had a problem were I had two nics and the clients computer was trying to run the script using a bad dns record. So it could not find the server and did not run. Also does this happen when you logoff or do a restart? I am having problems with me script not running when you do a cold boot or a restart but runs fine if you logoff and log back on. Hopes thishelps.

by rvkempen

JJustice might be partially right.
NT4 doen not know service records, so your w2k clients might "time out" while looking for their DC.
If you have not setup wins, i encourage you to do so, set up the wins service on one or both dc's (primary and secondary), point your dhcp settings to one or both, and set a wins node type (in a lan, with the wins servers in the same segment I would recommend 0x8, which means "first try the wins server, and if that fails try a broadcast").
If that fails also,you still have your dns fallback.

Good luck.

Ron.

by bejon.parsinia

Ok, we tweaked out DNS and WINS on the server and it seemed to help. However, we did some further research on our network needs and decided to upgrade to Win2K Advanced server. That should more than resolfe any logon script issues as our network will be 100% Win2K driven.

Thanks for your help gentlemen.

This discussion is closed to new replies.