Can't connect to Domain Controller on same Domain!

[tsap]

I have a domain of test.local, I have two Windows 2003 domain controllers setup.

Computer 2 can connect to computer 1 with the full DNS name of "comp1.test.local" and it works fine. But Computer 1 can't connect to computer 2 using the full DNS name of "comp2.test.local", It can only connect using "comp2"

this appers to be why I get event errors on both DC's.
I can event ID: 1925, which says It can't establish a link. and event ID: 1053, which says it can't determine the user or computer name.

Any Idea's?

 

[GlenJohnson]

http://www.kbalertz.com/kb_883271.aspx

Glen A. Johnson
If you're from the Illinois, Wisconsin or Florida area, check out Tek-Tips in Chicago IL
To get the best answers to your questions, check out faq950-5848

 

[tsap]

I don't have that problem, the link talks about.

 

[GlenJohnson]

What have you done to try and find the solution? I found that link on the first shot at google. Here's another.

http://www.microsoft.com/technet/pr...ons/7fcaa311-bc19-479d-9a4e-179704dfe08f.mspx

Glen A. Johnson
If you're from the Illinois, Wisconsin or Florida area, check out Tek-Tips in Chicago IL
To get the best answers to your questions, check out faq950-5848

 

[MTVW]

you are using WINS for resolution of the 2nd DC. Which is why when you ping -a the ip it resolves with just the name not the FQDN. Looks like there is not an A record configured for the 2nd DC.

 

[TheRing]

I agree with Saugilsr that it seems like a DNS problem. If he problem hasn't been solved I suggest that you enter a static DNS adress (pointing to the server 192.168.1.10) in the tcp/ip properties for 1 client and try to join the domain. Also you could try with clearing the dns cache of the client with the command: ipconfig /flushdns and the ipconfig /registerdns to register a new dns entry.

Best Regards Anders

 

[ryanjcole]

I wanted to say this:

I had the same type of problem and it resulted from changing a computer name at the same time I was registering it on the Domain.

I had to unjoin the domain before I could fix the name and then when I rejoined I was able to log in without any issue.
--
RC