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?
serendippityAsked:
Who is Participating?
 
GranModCommented:
PAQed with points refunded (500)

GranMod
Community Support Moderator
0
 
ImmediateActionCommented:
Can you confirm you have a valid AD DNS addresses on their network cards?
0
 
Jay_Jay70Commented:
Hi serendippity,

any errors under dcdiag?

Cheers!
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
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."
0
 
Jandakel2Commented:
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...
JK
0
 
dooleydogCommented:
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,
0
 
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.
0
 
Jay_Jay70Commented:
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
0
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.

All Courses

From novice to tech pro — start learning today.