| Author |
Message |
Scott
Guest
|
 Posted:
Sun Jan 16, 2005 5:13 am Post subject:
Migrated BDC cannot locate PDC to complete AD install |
|
|
I upgraded a NT 4.0 BDC to 2003. The AD wizard cannot find the Domain
Controller for the domain. All the clients (XP) are able to authenticate to
the Domain Controller, and have been able to for a few weeks. Why can this
BDC not see the domain controller? I can ping the DC using the DNS name, and
IP Address. |
|
| Back to top |
|
 |
Kevin D. Goodknecht Sr. [
Guest
|
| Posted:
Sun Jan 16, 2005 9:48 am Post subject:
Re: Migrated BDC cannot locate PDC to complete AD install |
|
|
In news:02248EBE-5E07-4248-AAF5-1A93655225FA@microsoft.com,
Scott <Scott@discussions.microsoft.com> commented
Then Kevin replied below:
| Quote: | I upgraded a NT 4.0 BDC to 2003. The AD wizard cannot
find the Domain Controller for the domain. All the
clients (XP) are able to authenticate to the Domain
Controller, and have been able to for a few weeks. Why
can this BDC not see the domain controller? I can ping
the DC using the DNS name, and IP Address.
|
Run netdiag /fix on the current DC. Post back with the ipconfig /all for the
BDC you upgraded.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
=================================== |
|
| Back to top |
|
|
Scott
Guest
|
| Posted:
Sun Jan 16, 2005 11:33 am Post subject:
Re: Migrated BDC cannot locate PDC to complete AD install |
|
|
Kevin,
Do you want me to run netdiag on the PDC (which already contains AD and DNS)
or the BDC that I'm trying to upgrade?
Scott
"Kevin D. Goodknecht Sr. [MVP]" wrote:
| Quote: | In news:02248EBE-5E07-4248-AAF5-1A93655225FA@microsoft.com,
Scott <Scott@discussions.microsoft.com> commented
Then Kevin replied below:
I upgraded a NT 4.0 BDC to 2003. The AD wizard cannot
find the Domain Controller for the domain. All the
clients (XP) are able to authenticate to the Domain
Controller, and have been able to for a few weeks. Why
can this BDC not see the domain controller? I can ping
the DC using the DNS name, and IP Address.
Run netdiag /fix on the current DC. Post back with the ipconfig /all for the
BDC you upgraded.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
|
|
|
| Back to top |
|
|
Scott
Guest
|
| Posted:
Sun Jan 16, 2005 11:39 am Post subject:
Re: Migrated BDC cannot locate PDC to complete AD install |
|
|
Here is the ipconfig /all info:
| Quote: | PDC
Host Name . . . . . . . . . . . . : slad01
Primary Dns Suffix . . . . . . . : eta.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : eta.com
Ehernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-11-43-D6-39-EC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.1.24
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
DNS Servers . . . . . . . . . . . : 172.16.1.24
BDC
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\WINNT\Profiles\Administrator.SLNT01>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : slnt01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : eta.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : eta.com
Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
Physical Address. . . . . . . . . : 00-90-27-28-5C-47
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
DNS Servers . . . . . . . . . . . : 172.16.1.24
Primary WINS Server . . . . . . . : 172.16.1.24
This is the details of the error I receive while trying to perform the AD
install:
DNS was successfully queried for the service location (SRV) resource
record
used to locate a domain controller for domain eta.com:
The query was for the SRV record for _ldap._tcp.dc._msdcs.eta.com
The following domain controllers were identified by the query:
slad01.eta.com
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or
are not running.
For information about correcting this problem, click Help.
|
"Kevin D. Goodknecht Sr. [MVP]" wrote:
| Quote: | In news:02248EBE-5E07-4248-AAF5-1A93655225FA@microsoft.com,
Scott <Scott@discussions.microsoft.com> commented
Then Kevin replied below:
I upgraded a NT 4.0 BDC to 2003. The AD wizard cannot
find the Domain Controller for the domain. All the
clients (XP) are able to authenticate to the Domain
Controller, and have been able to for a few weeks. Why
can this BDC not see the domain controller? I can ping
the DC using the DNS name, and IP Address.
Run netdiag /fix on the current DC. Post back with the ipconfig /all for the
BDC you upgraded.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
|
|
|
| Back to top |
|
|
Kevin D. Goodknecht Sr. [
Guest
|
| Posted:
Mon Jan 17, 2005 12:18 am Post subject:
Re: Migrated BDC cannot locate PDC to complete AD install |
|
|
In news:708BA883-F6E7-4E13-BF1E-753BFC49FD23@microsoft.com,
Scott <Scott@discussions.microsoft.com> commented
Then Kevin replied below:
| Quote: | Kevin,
Do you want me to run netdiag on the PDC (which already
contains AD and DNS) or the BDC that I'm trying to
upgrade?
|
Join the "BDC" to the domain as a member, then run netdiag /fix on both.
Also run dcdiag /fix on the DC.
BTW, PDC and BDC are NT4 terms in Win2k3 there are only DCs with role
holders.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
=================================== |
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Mon Jan 17, 2005 6:54 am Post subject:
Re: Migrated BDC cannot locate PDC to complete AD install |
|
|
Check you DNS too:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
Restart NetLogon on any DC if you change any of the above that
affects a DC and/or use:
nltest /dsregdns /server:DC-ServerNameGoesHere
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Lable domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
--
Herb Martin
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:644E2A00-925B-4822-AD1B-D5267731CB16@microsoft.com...
| Quote: | Here is the ipconfig /all info:
PDC
Host Name . . . . . . . . . . . . : slad01
Primary Dns Suffix . . . . . . . : eta.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : eta.com
Ehernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-11-43-D6-39-EC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.1.24
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
DNS Servers . . . . . . . . . . . : 172.16.1.24
BDC
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\WINNT\Profiles\Administrator.SLNT01>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : slnt01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : eta.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : eta.com
Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
Physical Address. . . . . . . . . : 00-90-27-28-5C-47
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
DNS Servers . . . . . . . . . . . : 172.16.1.24
Primary WINS Server . . . . . . . : 172.16.1.24
This is the details of the error I receive while trying to perform the
AD
install:
DNS was successfully queried for the service location (SRV) resource
record
used to locate a domain controller for domain eta.com:
The query was for the SRV record for _ldap._tcp.dc._msdcs.eta.com
The following domain controllers were identified by the query:
slad01.eta.com
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network
or
are not running.
For information about correcting this problem, click Help.
"Kevin D. Goodknecht Sr. [MVP]" wrote:
In news:02248EBE-5E07-4248-AAF5-1A93655225FA@microsoft.com,
Scott <Scott@discussions.microsoft.com> commented
Then Kevin replied below:
I upgraded a NT 4.0 BDC to 2003. The AD wizard cannot
find the Domain Controller for the domain. All the
clients (XP) are able to authenticate to the Domain
Controller, and have been able to for a few weeks. Why
can this BDC not see the domain controller? I can ping
the DC using the DNS name, and IP Address.
Run netdiag /fix on the current DC. Post back with the ipconfig /all for
the
BDC you upgraded.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
|
|
|
| Back to top |
|
|
Scott
Guest
|
| Posted:
Mon Jan 17, 2005 7:57 am Post subject:
Re: Migrated BDC cannot locate PDC to complete AD install |
|
|
Kevin,
Thanks for your continued support!
I tried to add the Server as a member server and I get an error, that the DC
cannot be located.
| Quote: | This is the details of the error I receive while trying to perform the AD
install:
DNS was successfully queried for the service location (SRV) resource
record
used to locate a domain controller for domain eta.com:
The query was for the SRV record for _ldap._tcp.dc._msdcs.eta.com
The following domain controllers were identified by the query:
slad01.eta.com
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or
are not running.
For information about correcting this problem, click Help.
|
"Kevin D. Goodknecht Sr. [MVP]" wrote:
| Quote: | In news:708BA883-F6E7-4E13-BF1E-753BFC49FD23@microsoft.com,
Scott <Scott@discussions.microsoft.com> commented
Then Kevin replied below:
Kevin,
Do you want me to run netdiag on the PDC (which already
contains AD and DNS) or the BDC that I'm trying to
upgrade?
Join the "BDC" to the domain as a member, then run netdiag /fix on both.
Also run dcdiag /fix on the DC.
BTW, PDC and BDC are NT4 terms in Win2k3 there are only DCs with role
holders.
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
|
|
|
| Back to top |
|
|
Kevin D. Goodknecht Sr. [
Guest
|
| Posted:
Mon Jan 17, 2005 8:15 am Post subject:
Re: Migrated BDC cannot locate PDC to complete AD install |
|
|
In news:FD1B6150-41C4-438A-B72C-EC478FF966F2@microsoft.com,
Scott <Scott@discussions.microsoft.com> commented
Then Kevin replied below:
| Quote: | Kevin,
Thanks for your continued support!
I tried to add the Server as a member server and I get an
error, that the DC cannot be located.
|
In the DNS management console check the properties of the eta.com zone, make
sure Allow dynamic updates is set to secure and unsecured or secure only.
You might try secure and unsecured first.
Then run netdiag /fix on the DC. Post the results from a netdiag /test:dns
/v
--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
=================================== |
|
| Back to top |
|
|
Brian O'Neil
Guest
|
| Posted:
Mon Jan 17, 2005 6:13 pm Post subject:
RE: Migrated BDC cannot locate PDC to complete AD install |
|
|
Make the primary DNS server of the BDC point to your PDC. AD uses DNS to
locate servers and the replica contained on your BDC is probably incomplete.
Once you have pointed it there and everything looks good, point it back to
itslef (the BDC).
-Brian
"Scott" wrote:
| Quote: | I upgraded a NT 4.0 BDC to 2003. The AD wizard cannot find the Domain
Controller for the domain. All the clients (XP) are able to authenticate to
the Domain Controller, and have been able to for a few weeks. Why can this
BDC not see the domain controller? I can ping the DC using the DNS name, and
IP Address.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in