Problem getting additional 2K DC onto 2K3 domain

  • Thread starter Thread starter Pride
  • Start date Start date
P

Pride

Ok... here is my situation:

I am trying to get a newly built win2K server to be a BDC on a win2K3
domain.

A little history first.

My domain controller is "davinci.companyname.com"
My domain is "companyname.com"
I made an error when I built the domain (2 years ago) by not naming it
"corporate.companyname.com" and I think this is the root of my
problem.

What is happening now?

I have a newly built win2K server authenticated on the domain. I can
see
the DC, access it’s shares, etc. I go to promote it via DCPROMO from
the Run
Command, and that is where my problems begin.

1. I select Add as an additional DC
2. I put in the UN/PW/Domain (Domain being "companyname"
3. It then asks me to Specify the full DNS name of the existing
domain.
4. I hit browse button, and it finds "companyname.com"
5. I select it, and hit NEXT and it says it cannot locate it.
6. I noticed that if I take the .COM off of hte end of it, it will
continue
on, but asks me "The Domain Controller "companyname" refers to the
domain
"companyname.com". Is that what you intended?"
7. I hit YES and it continues
8. DB and LOG locations, NEXT
9. Shared System Volume, NEXT
10. Directory Services Restore Mode Admin PW, I enter the PW I want,
NEXT
11. Summary, NEXT
12. Configuring AD comes up, and goes to work.
13. I get the error: "The Operation Failed Because: Failed finding
a
suitable domain controller for the domain.companyname.com. The
specified
domain either does not exist or could not be contacted"
14. Press OK, and the wizard exits.

_____________________________________________________

C:\Documents and Settings\Administrator.DAVINCI>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DAVINCI
Starting test: Connectivity
The host
dbf0f9fe-b723-4566-9856-d0947ea594b4._msdcs.noelkerhull.com co
uld not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(dbf0f9fe-b723-4566-9856-d0947ea594b4._msdcs.noelkerhull.com)
couldn’t
be resolved, the server name (DaVinci.noelkerhull.com)
resolved to
the
IP address (192.168.1.9) and was pingable. Check that the IP
address
is registered correctly with the DNS server.
......................... DAVINCI failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DAVINCI
Skipping all tests, because server DAVINCI is
not responding to directory service requests

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test
CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test
CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test
CheckSDRefDom

Running partition tests on : noelkerhull
Starting test: CrossRefValidation
......................... noelkerhull passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... noelkerhull passed test
CheckSDRefDom

Running enterprise tests on : noelkerhull.com
Starting test: Intersite
......................... noelkerhull.com passed test
Intersite
Starting test: FsmoCheck
......................... noelkerhull.com passed test
FsmoCheck

___________________________________________

Here is the IP Config Output
-------------------------------------------------
C:\Documents and Settings\Administrator.DAVINCI>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DaVinci
Primary Dns Suffix . . . . . . . : noelkerhull.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : noelkerhull.com

Ethernet adapter Davinci Team:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : BASP Virtual Adapter
Physical Address. . . . . . . . . : 00-0A-5E-44-29-51
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.9
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.9
---------------------------------------------------

I am NOT getting the ._msdcs.noelkerhull.com as a record in DNS.

I looked in the Event Viewer for DNS, and see about a million of the
following errors:

The DNS server encountered a packet addressed to itself on IP address
192.168.1.9. The packet is for the DNS name
"_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.noelkerhull.com.".
The
packet will be discarded. This condition usually indicates a
configuration
error.

Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server.
5) Root hints.

I looked in my DNS-DAVINCI-Forward Lookup Zones-noelkerhull.com

and here is a snapshot of what is there:

www Host (A) 24.137.12.195
davinci Host (A) 192.168.1.9
ftp Host (A) 192.168.1.9
webmail Host (A) 192.168.1.9

now, if I go to DNS-DAVINCI-Forward Lookup
Zones-noelkerhull.com-_msdcs

I see :

(same as parent folder) Name Server (NS)
davinci.noelkerhull.com

______________________________________________

Can anyone help me out here?
 
In
Pride said:
Ok... here is my situation:

I am trying to get a newly built win2K server to be a BDC
on a win2K3
domain.

A little history first.

My domain controller is "davinci.companyname.com"
My domain is "companyname.com"
I made an error when I built the domain (2 years ago) by
not naming it
"corporate.companyname.com" and I think this is the root
of my
problem.

What is happening now?

I have a newly built win2K server authenticated on the
domain. I can
see
the DC, access it's shares, etc. I go to promote it via
DCPROMO from
the Run
Command, and that is where my problems begin.

1. I select Add as an additional DC
2. I put in the UN/PW/Domain (Domain being "companyname"
3. It then asks me to Specify the full DNS name of the
existing
domain.
4. I hit browse button, and it finds "companyname.com"
5. I select it, and hit NEXT and it says it cannot
locate it.
6. I noticed that if I take the .COM off of hte end of
it, it will
continue
on, but asks me "The Domain Controller "companyname"
refers to the
domain
"companyname.com". Is that what you intended?"
7. I hit YES and it continues
8. DB and LOG locations, NEXT
9. Shared System Volume, NEXT
10. Directory Services Restore Mode Admin PW, I enter
the PW I want,
NEXT
11. Summary, NEXT
12. Configuring AD comes up, and goes to work.
13. I get the error: "The Operation Failed Because:
Failed finding
a
suitable domain controller for the
domain.companyname.com. The
specified
domain either does not exist or could not be contacted"
14. Press OK, and the wizard exits.

_____________________________________________________

C:\Documents and Settings\Administrator.DAVINCI>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DAVINCI
Starting test: Connectivity
The host
dbf0f9fe-b723-4566-9856-d0947ea594b4._msdcs.noelkerhull.com
co
uld not be resolved to an
IP address. Check the DNS server, DHCP, server
name, etc
Although the Guid DNS name

(dbf0f9fe-b723-4566-9856-d0947ea594b4._msdcs.noelkerhull.com)
couldn't
be resolved, the server name
(DaVinci.noelkerhull.com)
resolved to
the
IP address (192.168.1.9) and was pingable. Check
that the IP
address
is registered correctly with the DNS server.
......................... DAVINCI failed test
Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DAVINCI
Skipping all tests, because server DAVINCI is
not responding to directory service requests

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed
test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed
test
CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed
test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed
test
CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test
CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed
test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed
test
CheckSDRefDom

Running partition tests on : noelkerhull
Starting test: CrossRefValidation
......................... noelkerhull passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... noelkerhull passed test
CheckSDRefDom

Running enterprise tests on : noelkerhull.com
Starting test: Intersite
......................... noelkerhull.com passed
test
Intersite
Starting test: FsmoCheck
......................... noelkerhull.com passed
test
FsmoCheck

___________________________________________

Here is the IP Config Output
-------------------------------------------------
C:\Documents and Settings\Administrator.DAVINCI>ipconfig
/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DaVinci
Primary Dns Suffix . . . . . . . : noelkerhull.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : noelkerhull.com

Ethernet adapter Davinci Team:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : BASP Virtual Adapter
Physical Address. . . . . . . . . : 00-0A-5E-44-29-51
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.9
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.9
---------------------------------------------------

I am NOT getting the ._msdcs.noelkerhull.com as a record
in DNS.

I looked in the Event Viewer for DNS, and see about a
million of the
following errors:

The DNS server encountered a packet addressed to itself
on IP address
192.168.1.9. The packet is for the DNS name
"_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.noelkerhull.com.".
The
packet will be discarded. This condition usually
indicates a
configuration
error.

Check the following areas for possible self-send
configuration errors:
1) Forwarders list. (DNS servers should not forward to
themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record
for this DNS
server unless subzone is also on this server.
5) Root hints.

I looked in my DNS-DAVINCI-Forward Lookup
Zones-noelkerhull.com

and here is a snapshot of what is there:

www Host (A) 24.137.12.195
davinci Host (A) 192.168.1.9
ftp Host (A) 192.168.1.9
webmail Host (A) 192.168.1.9

now, if I go to DNS-DAVINCI-Forward Lookup
Zones-noelkerhull.com-_msdcs

I see :

(same as parent folder) Name Server (NS)
davinci.noelkerhull.com
Click to expand...

This is the default way Win2k3 sets this up, it is a delegation.

Can anyone help me out here?
Click to expand...

You should have a forward lookup zone named _msdcs.noelkerhull.com, if it is
not there, create it, allow dynamic updates on the zone and restart the
netlogon service.

Normally, this zone is set to replicate to all DNS servers in the forest,
but with that setting it won't replicate to Win2k, set it to replicate to
all domain controllers in the noelkerhull.com domain.
Point the Win2k to the Win2k3 for DNS before dcpromo and don't change it
until the zones replicate to the Win2k.
 
Kevin D. Goodknech1 said:
In


This is the default way Win2k3 sets this up, it is a
delegation.



You should have a forward lookup zone named
_msdcs.noelkerhull.com, if it is
not there, create it, allow dynamic updates on the zone and
restart the
netlogon service.

Normally, this zone is set to replicate to all DNS servers in
the forest,
but with that setting it won't replicate to Win2k, set it to
replicate to
all domain controllers in the noelkerhull.com domain.
Point the Win2k to the Win2k3 for DNS before dcpromo and don't
change it
until the zones replicate to the Win2k.
Click to expand...

Thank you for your assistance! Turns out the _mscds i had in DNS was
faulty. I removed it, then ran netdiag /fix and problem resolved.

Thank you for your assistance!
 
In
Pride said:
Thank you for your assistance! Turns out the _mscds i
had in DNS was
faulty. I removed it, then ran netdiag /fix and problem
resolved.
Click to expand...

It was not faulty, it was a delegation, you are supposed to have a separate
zone for _msdcs.companyname.com, although, the way you did it will work, it
is not the default behavior for Win2k3.
 
Back
Top