Discussion Locked

Desired Domain Controller To Log ON

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Q- There are mulitiple PDCs and BDCs in my Network (All NT Servers - Domain Controllers Trusted Domain Model) I want users to LOG ON to their closest Domain Controller whether it is a PDC or a BDC. Can you please tell me on how can I do this?

15 replies

by spydergst1

When a user logs in the account is handled by the closest PDC BDC by default. The domains sycronize frequantly.

I recommend logging into one Domain which gives access to all the other domain's resources via trusted relationships. The way you describe it here sounds like users are logging into different domains with access to all the same resources across the network.

by mutahirali

Actually it is simply understood that when a user logs on it is handled by PDC or BDC, but what i want to know is to "How Shall I Set the nearest DOMAIN CONTROLLER (A PDC or BDC) for users to log on to kill authentication traffic.."
I hope u will now better understand.
anyway thanks for all ur help.

by redeyes

This is an interesting question, therefore I am subscribing to this one. Maybe some of the real NT gurus out there will have a solution; however, I don't think that it is possible for the OS to know which controller is the closest. If I'm not mistaken, the "least busy" domain controller will be the first to answer the login request. Is there a WAN involved? How many trusted domains? How many BDC's per domain? Good Luck...

by redeyes

Looks like member "RSP" has solved this one! Good question, Great answer.
We learn something every day...

by doubledown

In reality, machines will log on to BDC's first. If you have a BDC and a PDC, the machine will always go to the BDC.
This isn't what is documented by Microsoft, but if you do a little testing, you will find it's true.

If you want to kill authentication traffic (broadcasts) you can do it by using subnets, or routers. Place a BDC in each subnet, and broadcast traffic is limited.

I've heard rumors that there was a way to tell a machine that you could specify a specific BDC for logon, but I haven't seen it yet.

by mutahirali

I have tried what you have said one year before and its true what you are saying but I have heard too that we can specify the desired domain controller.
your help in this regard is appreciated.
thanks alot Double Down:)

by frank.peeters

When a client wants to log on to a domain, it needs to find out which BDC's are available. The list of BDC's is maintained in a special Netbios 'group' name. Clients use either WINS or browsing to obtain this name. If you use WINS, you should see itin the WINS database with registration type 1C.

In normal circumstances the client will pick the BDC with the best response. However sometimes, e.g. when the local BDC has been down, a remote BDC could be chosen. The connection ('secure channel')will not switch back to the local BDC after it is up again, even if response times from the other BDC are horrible.

If you have multiple sites with a WINS server per site, you could control the 1C names by static registrations. In each site, create a static 1C record in the WINS database with only the IP address(es) of local BDC('s). The drawback is the administrative overhead: you have to remember to change the static entries every time a BDC address changes. Also, if you want to switch back to dynamic registrations, you need to reboot the PDC and then all BDC's after you deleted the static one.

Another remark: Netbios group names can only hold a maximum of 25 entries. The 26th registration will push out the oldest registered address. For a 1C name, the oldest registered address is the one from a BDC that has been up the longest. To see clients suddenly not being able to log in via the most stable BDC, can seem very strange.
A number of 25 addresses may be enough at first, butif your domain is spread over multiple small sites and if BDC's are multihomed, it can be very little.

by woody h

I experienced this problem at the previous network that I administered. The solution that we used was the LMHOST.SAM file. If you look in the C:\WINNT\SYSTEM32\DRIVERS\ETC folder, you will see the LMHOST file and many other files. Open the LMHostfile using Notepad. DO NOT associate any program with this file! There are instructions on how to configure the file in there, here is an example:
IP ADDRESS name(pdc or bdc)
xxx.xxx.xxx.xxx server-bdc #PRE #DOM:mydomain
xxx.xxx.xxx.xxx server1-bdc #PRE
xxx.xxx.xxx.xxx server2-bdc #PRE

And so on. The first server in the list, would be the server you want the workstation to log onto, and so on. Once you are done, save the file, and reboot the workstation. Now the workstation will logon to the server first on your list. One thing that you should realize, is that no matter what you do, if the server is too busy, the workstation will go to the next available server.

Woody

by rsp

Instead of all the others, and if you've tried them, you'll have to undo your changes, try:

NT Service pack 4 includes SETPRFDC which can be used to set a list of preferred domain controllers on NT

The syntax is: SETPRFDC

It can be used in a login script, and the list is remembered until it's run again.

This discussion is closed to new replies.