Unable to add Win Server 2003 machine to Win2k domain
 




IT Certification FAQ

 
|
Home
|
Microsoft
|
CISCO
|
CompTIA
|
Exam/Study FAQ
|
Employment FAQ
| Links  | Forums  |
Book Reviews


FAQFAQ  SearchSearch  MemberlistMemberlist  UsergroupsUsergroups  RegisterRegister  ProfileProfile  Log in to check your private messagesPrivate messages  Log inLog in

Unable to add Win Server 2003 machine to Win2k domain

 
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.general
Author Message
Dwight
Guest





PostPosted: Wed Apr 19, 2006 6:02 pm    Post subject: Unable to add Win Server 2003 machine to Win2k domain Reply with quote

I am unable to add a Windows Server 2003 (Win2k3) machine to a Win2k domain
(server is running Windows 2000 Server SP4).

I have run adprep /forestprep and adprep /domainprep on the Win2k machine.
Both ran successfully with no errors reported.

WinXP machines can be added to the domain with no trouble. Whether I try to
join the domain via Computer Name tab in System properties or add as a DC via
dcpromo, both report "An Active Directory domain controller for the domain
<NAME> could not be contacted."

I followed the troubleshooting/help steps. The query for the SRV record
returned the correct DC (we currently have only 1 server, the Win2k machine).
All of the resource records appear to be in DNS correctly.

I ran dcdiag.exe on the Win2k3 machine and it passed most tests. However,
the "DC discovery test" failed and reported the following:
"This computer cannot be joined to the domain named [TNT]. This is because
the following DNS names (A records) could not be resolved : [m]. Ask ...
[FATAL] Cannot find DC in domain 'TNT'. [ERROR_NO_SUCH_DOMAIN]"

Our server is named merlin so I don't know why it says it's trying to
resolve [m] in the dcdiag tool. We have a simple network in a development lab
with roughly 20 WinXP machines and static IP addresses.

Any help would be appreciated as the inability to add the Win2k3 Server to
provide IPv6 DNS is holding up development efforts. Thanks.
--
Thanks,

-Dwight
Back to top
Ken Aldrich
Guest





PostPosted: Wed Apr 19, 2006 9:47 pm    Post subject: Re: Unable to add Win Server 2003 machine to Win2k domain Reply with quote

I don't really have a homerun solution for you.
Try a netdiag /fix to repair your SRV records?

http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
http://support.microsoft.com/default.aspx?scid=kb;%5bLN%5d;555040


--
Ken Aldrich
DSRAZOR for Windows
Visual Click Software, Inc.
www.visualclick.com

"Dwight" <dwight@nospam.nospam> wrote in message
news:CE82C355-CA32-4AAE-B372-7E2B72F4E362@microsoft.com...
Quote:
I am unable to add a Windows Server 2003 (Win2k3) machine to a Win2k domain
(server is running Windows 2000 Server SP4).

I have run adprep /forestprep and adprep /domainprep on the Win2k machine.
Both ran successfully with no errors reported.

WinXP machines can be added to the domain with no trouble. Whether I try
to
join the domain via Computer Name tab in System properties or add as a DC
via
dcpromo, both report "An Active Directory domain controller for the domain
NAME> could not be contacted."

I followed the troubleshooting/help steps. The query for the SRV record
returned the correct DC (we currently have only 1 server, the Win2k
machine).
All of the resource records appear to be in DNS correctly.

I ran dcdiag.exe on the Win2k3 machine and it passed most tests. However,
the "DC discovery test" failed and reported the following:
"This computer cannot be joined to the domain named [TNT]. This is because
the following DNS names (A records) could not be resolved : [m]. Ask ...
[FATAL] Cannot find DC in domain 'TNT'. [ERROR_NO_SUCH_DOMAIN]"

Our server is named merlin so I don't know why it says it's trying to
resolve [m] in the dcdiag tool. We have a simple network in a development
lab
with roughly 20 WinXP machines and static IP addresses.

Any help would be appreciated as the inability to add the Win2k3 Server to
provide IPv6 DNS is holding up development efforts. Thanks.
--
Thanks,

-Dwight
Back to top
Dwight
Guest





PostPosted: Wed Apr 19, 2006 10:46 pm    Post subject: Re: Unable to add Win Server 2003 machine to Win2k domain Reply with quote

Thanks for the response Ken.

I ran netdiag /fix but no help there. I ran dcdiag on the Win2k server and
got the following error, could this be the reason that the Win2k3 server
can't join the domain?

The Active Directory may be prevented from starting.
Error event occured: EventID: 0x0000041B
Event string: The DHCP/BINL service has determined that it is ...........
MERLIN failed test systemlog

Thanks,

Dwight
--
Thanks,

-Dwight


"Ken Aldrich" wrote:

Quote:
I don't really have a homerun solution for you.
Try a netdiag /fix to repair your SRV records?

http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
http://support.microsoft.com/default.aspx?scid=kb;%5bLN%5d;555040


--
Ken Aldrich
DSRAZOR for Windows
Visual Click Software, Inc.
www.visualclick.com

"Dwight" <dwight@nospam.nospam> wrote in message
news:CE82C355-CA32-4AAE-B372-7E2B72F4E362@microsoft.com...
I am unable to add a Windows Server 2003 (Win2k3) machine to a Win2k domain
(server is running Windows 2000 Server SP4).

I have run adprep /forestprep and adprep /domainprep on the Win2k machine.
Both ran successfully with no errors reported.

WinXP machines can be added to the domain with no trouble. Whether I try
to
join the domain via Computer Name tab in System properties or add as a DC
via
dcpromo, both report "An Active Directory domain controller for the domain
NAME> could not be contacted."

I followed the troubleshooting/help steps. The query for the SRV record
returned the correct DC (we currently have only 1 server, the Win2k
machine).
All of the resource records appear to be in DNS correctly.

I ran dcdiag.exe on the Win2k3 machine and it passed most tests. However,
the "DC discovery test" failed and reported the following:
"This computer cannot be joined to the domain named [TNT]. This is because
the following DNS names (A records) could not be resolved : [m]. Ask ...
[FATAL] Cannot find DC in domain 'TNT'. [ERROR_NO_SUCH_DOMAIN]"

Our server is named merlin so I don't know why it says it's trying to
resolve [m] in the dcdiag tool. We have a simple network in a development
lab
with roughly 20 WinXP machines and static IP addresses.

Any help would be appreciated as the inability to add the Win2k3 Server to
provide IPv6 DNS is holding up development efforts. Thanks.
--
Thanks,

-Dwight


Back to top
Dwight
Guest





PostPosted: Thu Apr 20, 2006 12:36 am    Post subject: Re: Unable to add Win Server 2003 machine to Win2k domain Reply with quote

The results previously stated were from other dcdiag /test:<name> executions.
dcdiag /fix reports the following which may be the problem:

DNS test . . . . . . . . . . : Passed
[warning] Cannot find a primary authoritative DNS server for the name
'merlin.TNT.'. [RCODE_SERVER_FAILURE]
The name 'merlin.TNT' may not be registered in DNS.

Merlin is pointing to itself for DNS. In Forward Lookup Zones --> tnt there
is an A resource record for merlin with its IP address. Could the problem be
that the DNS server doesn't think it's authoritative?

Thanks,

Dwight



--
Thanks,

-Dwight


"Dwight" wrote:

Quote:
Thanks for the response Ken.

I ran netdiag /fix but no help there. I ran dcdiag on the Win2k server and
got the following error, could this be the reason that the Win2k3 server
can't join the domain?

The Active Directory may be prevented from starting.
Error event occured: EventID: 0x0000041B
Event string: The DHCP/BINL service has determined that it is ...........
MERLIN failed test systemlog

Thanks,

Dwight
--
Thanks,

-Dwight


"Ken Aldrich" wrote:

I don't really have a homerun solution for you.
Try a netdiag /fix to repair your SRV records?

http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
http://support.microsoft.com/default.aspx?scid=kb;%5bLN%5d;555040


--
Ken Aldrich
DSRAZOR for Windows
Visual Click Software, Inc.
www.visualclick.com

"Dwight" <dwight@nospam.nospam> wrote in message
news:CE82C355-CA32-4AAE-B372-7E2B72F4E362@microsoft.com...
I am unable to add a Windows Server 2003 (Win2k3) machine to a Win2k domain
(server is running Windows 2000 Server SP4).

I have run adprep /forestprep and adprep /domainprep on the Win2k machine.
Both ran successfully with no errors reported.

WinXP machines can be added to the domain with no trouble. Whether I try
to
join the domain via Computer Name tab in System properties or add as a DC
via
dcpromo, both report "An Active Directory domain controller for the domain
NAME> could not be contacted."

I followed the troubleshooting/help steps. The query for the SRV record
returned the correct DC (we currently have only 1 server, the Win2k
machine).
All of the resource records appear to be in DNS correctly.

I ran dcdiag.exe on the Win2k3 machine and it passed most tests. However,
the "DC discovery test" failed and reported the following:
"This computer cannot be joined to the domain named [TNT]. This is because
the following DNS names (A records) could not be resolved : [m]. Ask ...
[FATAL] Cannot find DC in domain 'TNT'. [ERROR_NO_SUCH_DOMAIN]"

Our server is named merlin so I don't know why it says it's trying to
resolve [m] in the dcdiag tool. We have a simple network in a development
lab
with roughly 20 WinXP machines and static IP addresses.

Any help would be appreciated as the inability to add the Win2k3 Server to
provide IPv6 DNS is holding up development efforts. Thanks.
--
Thanks,

-Dwight


Back to top
Display posts from previous:   
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.general All times are GMT
Page 1 of 1

 

Copyright © 2002-2006 Web-S-Sense Pty. Ltd. All rights reserved.

Powered by phpBB
Advertising | Policies/Disclaimers | Contact us | Link to us


Featured Sites: Free Antivirus and Antispyware Info | Free PC Support | MCSE Directory