Remote AD Site w/two DC's - Workstations not selecting good DC


we have remote ad site configured 2 dc's/gc's.  1 of dc's went down.  workstations not automatically getting logonserver up.

shouldn't workstations pick dc/gc working correctly?  i've been manually changing logonserver when calls.

thanks

what mean, "manually changing logonserver up."?  clients should using dclocator process track down available dc.  problem happens when users being unable contact dc workstation clients don't have second dns server defined in clients ip properties on network properties on workstation.

please post ipconfig /all client having problems.

--
paul bergson
mvp - directory services
mcitp: enterprise administrator
mcts, mct, mcse, mcsa, security+, bs csci
2008, vista, 2003, 2000 (early achiever), nt4
http://www.pbbergs.com    twitter @pbbergs
http://blogs.dirteam.com/blogs/paulbergson

please no e-mails, questions should posted in newsgroup. this
posting provided "as is" no warranties, , confers no rights.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Group Policy Event ID 1058 Error Code 1326 (The user name or password is incorrect)

Suspicious event log Event ID: 4905

DCOM received error "2147746132" from...