5 replies
by woody h
There are a few solutions to your problem.
1. Use the command setprfdc. Set preferred Domain controller. Be aware that if the domain controller that use set as the preferred is busy, it will authenticate with the next available DC.
2. In the LMHost file, put the PDC and BDCs in the order in which you would like the user to attempt authenticate with. For example:
xxx.xxx.xxx.xxx BDC1 #DOMAIN #PRE
xxx.xxx.xxx.xxx BDC2 #PRE
xxx.xxx.xxx.xxx BDC3 #PRE
and so on. If youlook in the LMHost file, you will see the examples that have listed. This is the way that I currently use.
3. Setup replication so that each and every domain controller contains all the login scripts.
Hope this helps.
Woody
by jjeff
by stevej
Although there is now way that i know of to set a preferred server as in Novell, ther are a couple of strageties you can use that may solve your problem
1) if your clients are configured as h-node Wins clients, they will communicat with thier WinsServer to get the address of a domain controler the use for authentication. with a bit of forethought you can configure your Wins server to direct client logon requests where you wish.
2) the stragety I prefer is the simpler one, although it may not be feasible depending on your enviorment. my preference to to use an LMHOSTS file to direct your clients to the domain controler you prefer. by using the #pre and #dom, you can load the addresses of the domain controlers you wish clients to use in the computers Netbios Name cache. in this way the first place they will look to for logon authenticatin is the first DC listed in thier cache.
good Luck,
SteveJ
by jjeff
by jjeff
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending