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?
nealbingAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chicagoanCommented:
Are there multiple domains? Workstation will default to the last domain logged into.

What does the proper domain's DC resolve to when this happens?

Are your DNS servers running on the DC's?
0
UkWizardCommented:
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
0
Casca1Commented:
Unless the domain selecteed isn't available (GCServer offline, unreachable), and then it will default to the local user profile, if that user has authenticated from that machine before. At which point, if you have multiple domains, the last authenticated domain would be the one used.
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

UkWizardCommented:
If it cannot find the domain you are trying to logon too, it will use the cached profile for that domain.
it will not authenticate against another domain to provide you access against the original domain.

Neal bang, i think you may need to elaborate more on whats happening.

Thanks

UkWizard.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Casca1Commented:
My apologies, I meant the credentials used for the last domain.
0
nealbingAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.