Adding a server to domain...

[DoahMonty]

Ok, I recently "resolved" an issue I was having with my PDC (see thread931-1405839). After doing so, I am now trying to re-add a new server (this used to be my old server, which is now reinstalled because of a virus). When I try to add it to the domain, or make it a secondary domain controller, it fails to see the current PDC. I am able to ping the current PDC by IP or name. The current PDC is 2003 server, and the server in which I'm trying to add is server 2000. The message I get when I try to add is...

"Network Identification

"The following error occurred validating the name "[domain name]". This condition may be caused by a DNS lookup problem. For information about troubleshooting common DNS lookup problems, please see the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=5171

The specified domain either does not exist or could not be contacted."

I tried everything I could find on Microsofts site with no success. Any suggestions are greatly appreciated.

 

[BridgeRE]

Can you or can you not add it to the domain as is? If not what mode is your domain in? 2003 native? If you can add it as is, can you just not dcpromo it?

 

[Cstorms]

The current 2003 DC/DNS server IP setup in the new member servers NIC properties?

Cory

 

[DoahMonty]

It is saying mixed mode. I cannot add it to the domain, nor can I promote it to a DC.

Cory... Are you asking me if my current PDC/DNS server is listed as a DNS server on the new server NIC properties... The answer to that is yes...

 

[DoahMonty]

Also, I feel I should add that with nslookup from the new server, everything appears to be working as far as DNS goes... But yet I still get the DNS error message when I try to add it to the domain... hmmm...

 

[BridgeRE]

Is it a ".local" domain?

 

[DoahMonty]

.com Sorry... should've mentioned that.

 

[BridgeRE]

....And you have tried both with, and without ".com"?

 

[DoahMonty]

yep. Even tried .local just incase I was dillusional in thinking it was .com... but it is .com for sure...

 

[DoahMonty]

Ok, i just wanted to give an update on this... As I said in a previous post, I am able to use nslookup from the machine I'm trying to add to the domain/promote to BDC. However, when I use nslookup on the PDC it cannot "connect" to any pc on the network. I copied and pasted my nslookup results below.

***********************************************************

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.COPYCATBS>nslookup server2005b
*** Can't find server name for address 192.168.2.250: Server failed
Server: UnKnown
Address: 192.168.2.250

*** UnKnown can't find server2005b: Server failed

C:\Documents and Settings\Administrator.COPYCATBS>nslookup server2005
*** Can't find server name for address 192.168.2.250: Server failed
Server: UnKnown
Address: 192.168.2.250

*** UnKnown can't find server2005: Server failed

C:\Documents and Settings\Administrator.COPYCATBS>nslookup ittechpc.copycatbs.co
m
*** Can't find server name for address 192.168.2.250: Server failed
Server: UnKnown
Address: 192.168.2.250

*** UnKnown can't find ittechpc.copycatbs.com: Server failed

C:\Documents and Settings\Administrator.COPYCATBS>nslookup servercomet
*** Can't find server name for address 192.168.2.250: Server failed
Server: UnKnown
Address: 192.168.2.250

*** UnKnown can't find servercomet: Server failed

C:\Documents and Settings\Administrator.COPYCATBS>nslookup servercomet.copycatbs
.com
*** Can't find server name for address 192.168.2.250: Server failed
Server: UnKnown
Address: 192.168.2.250

*** UnKnown can't find servercomet.copycatbs.com: Server failed

C:\Documents and Settings\Administrator.COPYCATBS>