Discussion Locked

NETLOGON follow up

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
This a follow-up of my question on NETLOGON error -- Event 3210. The logon error is gone, but it appears that some information is missing on the BDC. This could be Kixtart related. Anyhow, it appears user logon attempts first go to the BDC, and onlygo to the PDC on failure. How can I control the server that logs on user by default? Will the faster server always logon users?

4 replies

by spiceman

The server that logs on the user is usually related to physical proximity rather than speed. To reduce the BDC user login requires the BDC be placed furthest from the users and the PDC nearer the user in terms of cable length and network segments.

by andy_p

There is a tool called SETPRFDC - came with SP4. This allows you to set the logon DC,I think the main drawback is that if the preferred DC is not available the user cannot log on.

The DC that logons you on this the first to respond to the client request, it's usually the machine with the least load at that moment of time...I'm not aware of cable distance playing a big part

This discussion is closed to new replies.