General discussion

Locked

NETLOGON follow up

By bkubai ·
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?

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
Thread display: Collapse - | Expand +

All Comments

Collapse -

NETLOGON follow up

by spiceman In reply to NETLOGON follow up

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.

Collapse -

NETLOGON follow up

by bkubai In reply to NETLOGON follow up
Collapse -

NETLOGON follow up

by Andy_P In reply to NETLOGON follow up

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

Collapse -

NETLOGON follow up

by bkubai In reply to NETLOGON follow up
Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums