Link to home
Start Free TrialLog in
Avatar of jskfan
jskfanFlag for Cyprus

asked on

Domain Logonserver

Domain Logonserver
I have 2 AD sites, site1 and site2 and both of them have domain controllers which are also DNS servers.

in site1 when I join a computer to the domain it takes too long to show up up in AD.
By chance I run the SET command  in the computer that I joined to the domain and it shows that logonserver is the domain controller in site2.

Can someone tell me the reason why it's taking the logonserver in different site than the local site?

thanks
Avatar of Don
Don
Flag of United States of America image

Avatar of jskfan

ASKER

I did and AD sites and services work properly...
The issue I have is just with one computer so far.
Have you checked the event log for any errors
 
possibly mentioned here
http://technet.microsoft.com/en-us/library/bb727057.aspx 
Avatar of jskfan

ASKER

I am receiving the event ID 4 Kerberos
Avatar of jskfan

ASKER

I can't even join the computer to the domain
I receive the following message when I try to join the computer to the domian
"The following error occurred attempting to join the domain "xyz": Logon Failure: The target account name is incorrect."

ASKER CERTIFIED SOLUTION
Avatar of Don
Don
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jskfan

ASKER

you are getting enough points from redirecting me to web links...Lol
LOL....Dont want any trouble with copy/pasting from the link. Yeah, you seem to ask alot of questions I'm familiar with ;^D
BTW, I have encountered this before and have used the method mentioned in the link.
Avatar of jskfan

ASKER

Wow fixed it in a weird way...

I shutdown the DC that is in the same site as the computer I am trying to join to the domain.
That means when I tried to join the computer to the domain it queried the DC in the remote site since the DC in the local site was shut down.
and boom it says welcome to mydomain.com

to summarize it, there should be a problem with the local DC