Unable to add new DC.

  • Thread starter Thread starter MarcAnthony
  • Start date Start date
M

MarcAnthony

Hello everyone and thanks in advance for any help or suggestions.

Here's my scenario.

I have a brand new server and just installed Windows 2000 Server SP4. The
problem is when trying to add it as an additional domain controller I get
the following error " The domain cannot be contacted and ends with go to
http://go.microsoft.com/fwlink/?linkid=5171" . I've been up and down the
Microsoft site and tried many things. In my DNS on the existing domain
controller everything seems Ok. One thing that I don't see is the _MSDCS,
_SITES, _TCP or _UDP subfolders.

The name under ADU&C is town***.com.

Here is the full IPCONFIG

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : twpdc
Primary DNS Suffix . . . . . . . : town***.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : town***.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3163
Physical Address. . . . . . . . . : 00-08-02-46-25
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2


Regards,
Marc
 
In
MarcAnthony said:
Hello everyone and thanks in advance for any help or suggestions.

Here's my scenario.

I have a brand new server and just installed Windows 2000 Server SP4.
The problem is when trying to add it as an additional domain
controller I get the following error " The domain cannot be contacted
and ends with go to http://go.microsoft.com/fwlink/?linkid=5171" .
I've been up and down the Microsoft site and tried many things. In my
DNS on the existing domain controller everything seems Ok. One thing
that I don't see is the _MSDCS, _SITES, _TCP or _UDP subfolders.

The name under ADU&C is town***.com.
Click to expand...

Your ipconfig looks good your domain name matches you primary DNS suffix,
the next thing to look at is are dynamic updates set to "Yes" on the forward
lookup zone and is the DHCP client service running? The DHCP client service
is responsble for dynamic updates.
What services are disabled?
 
Yes is selected in dynamic updates and DHCP is running.
The server options point to the internal DNS server. Of
all of the things I have checked the only thing I see missing
is the _MSDCS, _SITES, _TCP or _UDP subfolders.

Marc
 
In
MarcAnthony said:
Yes is selected in dynamic updates and DHCP is running.
The server options point to the internal DNS server. Of
all of the things I have checked the only thing I see missing
is the _MSDCS, _SITES, _TCP or _UDP subfolders.

Marc
Click to expand...

As long as :
1. town***.com is the name of the zone in DNS,
2. Dynamic Updates set to at least Yes
3. Primary DNS suffix is town***.com
4. Pointing to your own DNS only
5. The AD DNS domain name is town***.com (as it shows up in ADUC).

Then it should pretty much just work.

You have most of these done from what I read. Let's look at the AD domain
name. DOes it match?

Once all this done, perform this simple procedure to register:

ipconfig /registerdns
net stop netlogon
net start netlogon

Let us know how you make out.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
MarcAnthony said:
Yes is selected in dynamic updates and DHCP is running.
The server options point to the internal DNS server. Of
all of the things I have checked the only thing I see missing
is the _MSDCS, _SITES, _TCP or _UDP subfolders.

Marc
Click to expand...
Can you post the ipconfig for the DC you are trying to add?
 
Yes the AD domain name matches and the
ipconfig /registerdns
net stop netlogon
net start netlogon
has been done to no avail.

Marc
 
Here is the IPCONFIG from the new server.

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ZOOM
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC
Physical Address. . . . . . . . . : 00-50-8B-2C-
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 119.0.0.241
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 119.0.0.2
DNS Servers . . . . . . . . . . . : 119.0.0.199


Thanks for all your help.

Marc
 
In MarcAnthony <[email protected]> posted a question
Then Kevin replied below:

This DC has a disjointed name space because there is no Primary DNS suffix.
That is why the Folders are not being created. If you will email me directly
to verify a good email address (make sure you de-munge my email address), I
can help you fix this with a script you can run.
 
This machine is a stand alone server right now. I've been trying to add it
as a DC to an existing domain. The
folders are not being created on the DNS server. This server is not in
action yet.
You can email me the script at "support at townofws dot com" if you think
it will be helpful. Once again thanks
for all your help.

Marc
 
In
MarcAnthony said:
This machine is a stand alone server right now. I've been trying to
add it as a DC to an existing domain. The
folders are not being created on the DNS server. This server is not in
action yet.
You can email me the script at "support at townofws dot com" if you
think it will be helpful. Once again thanks
for all your help.

Marc
Click to expand...
OK I get it now, it won't have a suffix unless it is a member of the domain.
But it must point to the DC for DNS before you can join it. But if the SRV
records are not being created you won't be able to join any machine to the
domain.
We need to fix the DC before you can join any machines.
Run DCDIAG /v and netdiag /test:dns /v on the DC and email them to me there
is a 100kb limit on posts and they are too big to post here. Maybe I can
find the problem on the DC.

When you said DHCP service was running are you referring to the DHCP server
or DHCP Client? The DHCP client is required.
 
Yes the DHCP client is running. I tried running those commands and they were
not found. Are they on the Windows 2000 diagnostics CD?

Marc
 
In
MarcAnthony said:
Yes the DHCP client is running. I tried running those commands and
they were not found. Are they on the Windows 2000 diagnostics CD?

Marc
Click to expand...
They are both on the server support tools on the CD or you can download
updated versions from Microsoft at http://download.microsoft.com just do a
search for dcdiag and netdiag.
 
This box is pointing to itself for DNS. It needs to point at the DC for DNS. That will solve the problem.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
No it's not.

IP Address. . . . . . . . . . . . : 119.0.0.241
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 119.0.0.2
DNS Servers . . . . . . . . . . . : 119.0.0.199

Marc


Michael Johnston said:
This box is pointing to itself for DNS. It needs to point at the DC for
Click to expand...
DNS. That will solve the problem.
Thank you,
Mike Johnston
Microsoft Network Support
Click to expand...
rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
Click to expand...
message are best directed to the newsgroup/thread from
 
In
MarcAnthony said:
Here is the IPCONFIG from the new server.

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ZOOM
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC
Physical Address. . . . . . . . . : 00-50-8B-2C-
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 119.0.0.241
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 119.0.0.2
DNS Servers . . . . . . . . . . . : 119.0.0.199
Click to expand...
If you want to add this to you domain you need to fix its IP addresses and
point it to 192.168.2.2 for DNS where did you come up with these IP
addresses?
 
Kevin,

Just want to add for the MarcAnthony , BEFORE a server is promoted, the
Primary DNS Suffix must be set. That name has to match the DNS zone name and
the AD name. The netlogon service uses this name to find the name on the DNS
server to register into.



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
I'm not sure what IP the DNS server is that is hosting the zone name for
DNS, but Michael is talking about that server. If DNS is installed on
119.0.0.199, then that is a good thing. But the SRV records must be there.
If the first DC is not registering this data, then that's why it won't
"find" the domain. So whatever IP that DNS is on that is supposedly hosting
the AD zonename, is what needs to be here.

As Kevin mentioned, if the Primary DNS Suffix is set on the first DC, and
the nameis the same as the AD DNS name, and it is not a single label name
(such as domain instead of domain.com or domain.net, etc), then it should be
registering. If the first DC has a disjointed namespace, that script Kevin
mentioned will work for you. Once the SRVs are registered, then everything
else will work, including adding another DC.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Sorry about that my mistake, I posted the wrong info.

The IPCONFIG on the new server is

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ZOOM
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC
Physical Address. . . . . . . . . : 00-50-8B-2C-
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.241
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2

192.168.2.2 is the DC with DNS.

Marc
 
In
MarcAnthony said:
Sorry about that my mistake, I posted the wrong info.

The IPCONFIG on the new server is

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ZOOM
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NIC
Physical Address. . . . . . . . . : 00-50-8B-2C-
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.241
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2

192.168.2.2 is the DC with DNS.
Click to expand...

This is the one you want to DCPROMO, correct?
Before you promote this box join it to the domain as a member and set it to
change the DNS suffix if domain membership changes.
After it is a member it should have the correct Suffix then you should be
able to promote it to a DC, provided the current DC is running without DNS
errors.
 
Ok I'll try that and report back.

Marc


Kevin D. Goodknecht said:
In

This is the one you want to DCPROMO, correct?
Before you promote this box join it to the domain as a member and set it to
change the DNS suffix if domain membership changes.
After it is a member it should have the correct Suffix then you should be
able to promote it to a DC, provided the current DC is running without DNS
errors.
Click to expand...
 
Back
Top