nealbing
asked on
2000 Professional Clients logging into the wrong domain
What would cause 2000 Professional computers to log into the wrong domain on a 2003 Server network? Sometimes the computers log into correct domain and sometimes they want. Am I looking at a DNS problem or is this an Active Directory Sites and Services problem? I am leaning toward Sites and Services because I read that it can control authentication. Can anyone give an explanation or soloution to this problem?
Sounds more like the user is accidentally selecting the wrong domain in the drop down box at the logon prompt.
It cannot be loggin into the wrong domain, only what is selected at the logon prompt drop down box.
Regards
UkWizard
It cannot be loggin into the wrong domain, only what is selected at the logon prompt drop down box.
Regards
UkWizard
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
My apologies, I meant the credentials used for the last domain.
ASKER
Casca1 and UkWizard, sorry for my delayed response to your questions. Both of your suggestions are very good and have put me on the right track to solving this login problem.
It never occured to me that the local client machine would authenticate to the last server that it logged into. Also I never new that the client machine will never authenticate against another domain to provide access against the original domain. I figured since the 2000 server infrastructure is peer to peer with no master that it would not matter. Apparently I was very wrong on that one. I believe that is the main problem I was having with my client machines when it could not log into the servers possibly. Once again thank you all for putting me on the right track.
It never occured to me that the local client machine would authenticate to the last server that it logged into. Also I never new that the client machine will never authenticate against another domain to provide access against the original domain. I figured since the 2000 server infrastructure is peer to peer with no master that it would not matter. Apparently I was very wrong on that one. I believe that is the main problem I was having with my client machines when it could not log into the servers possibly. Once again thank you all for putting me on the right track.
What does the proper domain's DC resolve to when this happens?
Are your DNS servers running on the DC's?