force logonserver to local BDC

[Peta Power]

We have a NT4 domain and Windows 2000 clients.
For some reason when logging on users are going to the PDC
and not being validated by the local BDCs at the site.
Regedit has a volatile environment setting but it doesn't
seem to make any difference. Our HO support suggest
cutting the WAN and then logging on but there must be a
better way.

Any ideas.

 

[Brian Oakes [MSFT]]

Try this, on your local BDC see which Wins server it points do. Then in the
wins server, check the DOMAIN[1ch] group record in the table for the IP of
this BDC.

This is the record your clients look for when they login. They take the
domain 1c entries and then take all the IP's in it and send a netlogon frame
to each one and then are authenticated with the first dc that responds. In
all honestly it could be that the DC in the HO is actually responding first.
In that case the local BDC might be too busy hence responding slower.

The only way to bypass this process if to create an lmhosts file on the
client that forces them to the local bdc. (Not a good idea). You can have
your network folks take a trace and review the traffic when a client logs
in. Then you can watch the network traffic and see who is responding first.
I hope that help and gets you in the right direction!

--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.