One domain controller is requesting password to access other domain controller

We have two servers which both authenticate users on our Win2003 server network. All of a sudden, when I try to browse to Server1 from Server2 (My Network Places, Entire Network, Microsoft Windows Network, Domain, Server1, a dialogue box appears asking for a Username and Password. This has only just started to occur. If I enter the normal administrator credentials in whatever format, I am told logon is unsuccessful.  I do not get a similar request for credentials when I browse to Server2 from Server1. What is going on?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Can you confirm you have a valid AD DNS addresses on their network cards?
Hi serendippity,

any errors under dcdiag?

serendippityAuthor Commented:
ImmediateAction:  DNS addresses are valid and okay. This problem has only recently arisen.

Jay Jay70:  I have done a search for dcdiag and two entries came up: one in c:\supporttools and another in c:\windows\servicepackfiles\i386. I am not sure how to run the tool. I opened a command prompt and ran c:dcdiag, but received a message that "dcdiag" is not recognised as an internal or external command, operable program or batch file."
Webinar: Cyber Crime Becomes Big Business

The rising threat of malware-as-a-service is not one to be overlooked. Malware-as-a-service is growing and easily purchased from a full-service cyber-criminal store in a “Virus Depot” fashion. Join us in our upcoming webinar as we discuss how to best defend against these attacks!

You will need to copy the dcdiag.exe file into the c:\windows\system 32 directory in order to run it from command prompt.  Also try netdiag (use same method)  Look for any errors that may stick out in the Event Viewer of the offending server also, and give us a report...
are they replicating properly?

make sure that you can connect to each server with the name, and not just the IP address.

DNS is crucial for proper Active Directory functions. Make sure that your DNS and zones are setup correctly.

Good Luck,
serendippityAuthor Commented:
This issue has now been resolved (somehow) following an upgrade of the forest functional level to Windows 2003 (from default Windows 2000). Not sure of the precise mechanism, but some process in Active Directory seems to have been put in train by the upgrade which resulted in the issue being resolved. If anyone can suggest a reason, please let me know. Thanks for your contributions, but this question is now closed without award of points.
make sure you close it for us :)

post in community support and ask for it to be closed, otherwise it gets left open and has to get cleaned up later
PAQed with points refunded (500)

Community Support Moderator

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
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

From novice to tech pro — start learning today.