set command and logonserver

[Luvsql]

We were running into issues with our CRM server and found that we manually had to restart the logon service as it was not restarting in the proper order.

A question that came up was when running the set command on our servers, the LOGONSERVER= is actually pointing to our backup domain controller instead of our domain controller. I don't know what affect this has, but could this cause any sort of authentication performance issues? Should it point to the live domain controller? Was this a manual change or did it set this up itself?

 

[WhoKilledKenny]

Actually if I am not mistaken, when you run the set command it is just telling you which server authenticated you on the domain. The next time you logon you may see LOGONSERVER=\\MYPDC
This is not a hard coding of which DC is used for authentication. Any DC in your environment (site) should be able to authenticate you.

 

[itsp1965]

The logonserver variable indicates where clients authenticate to (changing this set via modify the set variable doesn't work). You indicated this is a BDC (is this NT4 or are u referring to an AD controller)
In NT the BDC closest to you would usually handle your authentication requests.
In AD it would also be the DC that is closest to you (usually -- but not necessarily). Setting up AD sites will help in ensuring that your clients access the DC that is closest to you.
Hope this helps.

 

[arrow483]

WKKenny is right. It contains the server that answered the logon request, and may vary each logon. While you can force the variable to another value, it has no effect on who will authenticate. It just reports who did.

 

[juniper911]

If you did want users to get authenticated by a particular server becuase it has better hardware you can up its priority or weighting in DNS. It depends if the "backup" DC and the "live" DC are in the same site. You dont want users to be authenticated from a DC in another site.