| Author |
Message |
Scott
Guest
|
 Posted:
Sun Jan 16, 2005 5:01 am Post subject:
Migrate BDC cannot locate the Domain Controller |
|
|
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 |
|
 |
Marina Roos [SBS-MVP]
Guest
|
| Posted:
Sun Jan 16, 2005 5:20 am Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
| 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 |
|
|
Scott
Guest
|
| Posted:
Sun Jan 16, 2005 5:41 am Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
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.
"Marina Roos [SBS-MVP]" wrote:
| Quote: | Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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 |
|
|
SuperGumby [SBS MVP]
Guest
|
| Posted:
Sun Jan 16, 2005 6:38 am Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
actually, I didn't think that what you've done was possible.
I'm pretty sure that if you want to move from a 'domain' to an 'active
directory' you need to first upgrade the PDC. The bit I didn't think was
possible is a W2K3 server acting as a BDC in an NT domain. Or has the
upgrade made the 2k3 machine a simple 'member server'?
I was looking for something to do. Where did I put that NTS CD?
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
| 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 |
|
|
Scott
Guest
|
| Posted:
Sun Jan 16, 2005 6:53 am Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
I'm sorry, I left that bit of info out. Yes, the PDC was upgraded earlier in
the month. This BDC was serving as a BDC in an Active Directory domain, which
had previously been upgraded from NT 4.0.
"SuperGumby [SBS MVP]" wrote:
| Quote: | actually, I didn't think that what you've done was possible.
I'm pretty sure that if you want to move from a 'domain' to an 'active
directory' you need to first upgrade the PDC. The bit I didn't think was
possible is a W2K3 server acting as a BDC in an NT domain. Or has the
upgrade made the 2k3 machine a simple 'member server'?
I was looking for something to do. Where did I put that NTS CD?
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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 |
|
|
SuperGumby [SBS MVP]
Guest
|
| Posted:
Sun Jan 16, 2005 9:14 am Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
are either of these boxes SBS?
Actually, more importantly, is/was Exchange installed on either box?
Your IPConfig looks OK and I can't suggest why you're getting your error,
I'd like to investigate fixing the problem of your incorrectly named AD DNS
space first though.
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:AA446597-63B8-4967-986A-C17F6A5AA49C@microsoft.com...
| 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.
"Marina Roos [SBS-MVP]" wrote:
Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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 |
|
|
Scott
Guest
|
| Posted:
Sun Jan 16, 2005 9:41 am Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
No, neither are SBS or Exchange.
Please excuse my ignorance, but why is my AD DNS incorrectly named?
"SuperGumby [SBS MVP]" wrote:
| Quote: | are either of these boxes SBS?
Actually, more importantly, is/was Exchange installed on either box?
Your IPConfig looks OK and I can't suggest why you're getting your error,
I'd like to investigate fixing the problem of your incorrectly named AD DNS
space first though.
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:AA446597-63B8-4967-986A-C17F6A5AA49C@microsoft.com...
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.
"Marina Roos [SBS-MVP]" wrote:
Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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 |
|
|
Matt Gibson
Guest
|
| Posted:
Sun Jan 16, 2005 2:38 pm Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
Scott,
This newsgroup is for Small Business Server. Try the
Microsoft.public.windows.server.general newsgroup.
-Matt
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:2277E7E7-9B52-4C0B-9E81-9BC3B5415242@microsoft.com...
| Quote: | No, neither are SBS or Exchange.
Please excuse my ignorance, but why is my AD DNS incorrectly named?
"SuperGumby [SBS MVP]" wrote:
are either of these boxes SBS?
Actually, more importantly, is/was Exchange installed on either box?
Your IPConfig looks OK and I can't suggest why you're getting your error,
I'd like to investigate fixing the problem of your incorrectly named AD
DNS
space first though.
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:AA446597-63B8-4967-986A-C17F6A5AA49C@microsoft.com...
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.
"Marina Roos [SBS-MVP]" wrote:
Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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 |
|
|
Scott
Guest
|
| Posted:
Sun Jan 16, 2005 7:51 pm Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
Matt,
I know, I accidently posted to the incorrect group. But, I have received
some good support, and think that the problem is near completion. I would
hate to have to start over.
"Matt Gibson" wrote:
| Quote: | Scott,
This newsgroup is for Small Business Server. Try the
Microsoft.public.windows.server.general newsgroup.
-Matt
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:2277E7E7-9B52-4C0B-9E81-9BC3B5415242@microsoft.com...
No, neither are SBS or Exchange.
Please excuse my ignorance, but why is my AD DNS incorrectly named?
"SuperGumby [SBS MVP]" wrote:
are either of these boxes SBS?
Actually, more importantly, is/was Exchange installed on either box?
Your IPConfig looks OK and I can't suggest why you're getting your error,
I'd like to investigate fixing the problem of your incorrectly named AD
DNS
space first though.
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:AA446597-63B8-4967-986A-C17F6A5AA49C@microsoft.com...
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.
"Marina Roos [SBS-MVP]" wrote:
Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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 |
|
|
Matt Gibson
Guest
|
| Posted:
Sun Jan 16, 2005 7:51 pm Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
*Grin*
I'm not telling you to. Just making sure you know why Gumby was asking all
those SBS questions.
You're in over my head in NT land here :)
-Matt
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:CF10D02E-17BF-42C7-B142-AE56CFEA2B3F@microsoft.com...
| Quote: | Matt,
I know, I accidently posted to the incorrect group. But, I have received
some good support, and think that the problem is near completion. I would
hate to have to start over.
"Matt Gibson" wrote:
Scott,
This newsgroup is for Small Business Server. Try the
Microsoft.public.windows.server.general newsgroup.
-Matt
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:2277E7E7-9B52-4C0B-9E81-9BC3B5415242@microsoft.com...
No, neither are SBS or Exchange.
Please excuse my ignorance, but why is my AD DNS incorrectly named?
"SuperGumby [SBS MVP]" wrote:
are either of these boxes SBS?
Actually, more importantly, is/was Exchange installed on either box?
Your IPConfig looks OK and I can't suggest why you're getting your
error,
I'd like to investigate fixing the problem of your incorrectly named
AD
DNS
space first though.
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:AA446597-63B8-4967-986A-C17F6A5AA49C@microsoft.com...
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.
"Marina Roos [SBS-MVP]" wrote:
Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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 |
|
|
SuperGumby [SBS MVP]
Guest
|
| Posted:
Mon Jan 17, 2005 12:18 am Post subject:
Re: Migrate BDC cannot locate the Domain Controller |
|
|
you should _NEVER_ name your AD DNS as your internet FQDN.
as there is no SBS nor Exchange I'd fix this first.
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:2277E7E7-9B52-4C0B-9E81-9BC3B5415242@microsoft.com...
| Quote: | No, neither are SBS or Exchange.
Please excuse my ignorance, but why is my AD DNS incorrectly named?
"SuperGumby [SBS MVP]" wrote:
are either of these boxes SBS?
Actually, more importantly, is/was Exchange installed on either box?
Your IPConfig looks OK and I can't suggest why you're getting your error,
I'd like to investigate fixing the problem of your incorrectly named AD
DNS
space first though.
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:AA446597-63B8-4967-986A-C17F6A5AA49C@microsoft.com...
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.
"Marina Roos [SBS-MVP]" wrote:
Hi Scott,
Please post the ipconfig/all from both servers.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"Scott" <Scott@discussions.microsoft.com> schreef in bericht
news:3631BB67-8266-47B6-B53C-ECD6805F881A@microsoft.com...
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