Adding XP Pro to NT Domain

[bivonaj]

Trying to add a XP pro machine to a NT Domain and
receiving the following error:

Note: This information is intended for a network
administrator. If you are not your network's
administrator,
notify the administrator that you received this
information,
which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.

The domain name might be a NetBIOS domain name. If this
is the case, verify that the domain name is properly
registered with WINS.

If you are certain that the name is not a NetBIOS domain
name, then the following information can help
you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the
service location (SRV) resource record used to
locate a domain controller for domain DomainName:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.DomainName
Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include
delegation to its child zone:

\\DOMAIN
.. (the root zone)

Any Help would be appreciated

 

[Doug Sherman [MVP]]

Try:

1. On the NT PDC, create the workstation account in Server Manager.

2. On the XP machine create an lmhosts file per the following and reboot:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314108

3. If the XP machine is currently joined to some other domain, join it to a
workgroup and reboot.

4. Attempt to join the NT domain on the computer name tab in System
properties.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Ron Lowe]

Trying to add a XP pro machine to a NT Domain and
receiving the following error:

Note: This information is intended for a network
administrator. If you are not your network's
administrator,
notify the administrator that you received this
information,
which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.

The domain name might be a NetBIOS domain name. If this
is the case, verify that the domain name is properly
registered with WINS.

If you are certain that the name is not a NetBIOS domain
name, then the following information can help
you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the
service location (SRV) resource record used to
locate a domain controller for domain DomainName:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.DomainName
Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include
delegation to its child zone:

\\DOMAIN
. (the root zone)

Any Help would be appreciated

It can't find the domain controller.
This is usually a name resolution problem, as the error states.

Since it's an NT4 domain, it *is* a NetBIOS domain name.
So the problem is with NetBIOS name resolution, not DNS.
I'd want to try a bunch of diagnostics first...

Where is the NT4 domain controller?
Is it on the local subnet, or is it across a router from you?

Can you ping the domain controller's IP address?
Can you ping the domain controller's name?
Can you "net view \\domain-controller-name" from the command prompt?

What is the NodeType reported by an "ipconfig /all"?

Is there a WINS server in use?
If so, is it listed in the TCP/IP properties?
Can it be pinged?
Does it contain a Domain-name<1C> entry?


You can force it to resolve the IP address of a domain controller
by using an LMHOSTS file as indicated by Doug Sherman, but it
should be possible to repair normal name resolution methods.

 

[Guest]

Mr. Lowe,
I am having the same difficulty(error), and I can see many others have also. I just need help understanding your questions. I have a simple retail server system consisting of a server running NT Server 4.0(domain TW22, computer name BACKROOM1, a cash register running NT Workstation(domain TW22, computer name RG1, and I just added the XP Pro computer in place of a Win 98 machine(domain TW22, and computer name BACKROOM2). I unplugged the Win98 machine from the network and in its place put the new XP Pro machine. I ran the network wizard on the XP Pro machine and yet neither the NT machine or the XP machine list each other in their respective "Network Neighborhoods." On the XP machine, I have gone into System Settings and used the Computer Name tab to rename the XP machine BACKROOM2 with the Domain TW22. I also pinged the server IP address as indicated by ipconfig as being 10.10.10.0 and the ping failed. Why did it fail? The server and computers are connected with a 3Com eight port hub, all computers are lit on the hub. The network adaptor cards are indicating that there are no problems. What have I not done to make this simple connection work?
What do you mean by "Where is the NT4 domain controller?" Do you mean in my case TW22, or is there some physical controller that I just don't know about? The Network Neighborhood on this server consists of ENTIRE NETWORK, MICROSOFT WINDOWS NETWORK, TW22, BACKROOM1, REG1.

How do you ping the domain controllers name?

If I see a NodeType reported by an ipconfig /all command what am I to do with that information?

How do I check to see if a WINS Server is in use? And if so how do I ping it? And how do I check to see if it contains a Domain-name<1C> entry?

Any assistance you can provide in answering these questions so that I can understand what to do to set up this computer would be greatly appreciated. It amazes me that you have to spend so much time repeatedly answering the same issue over and over again. It seems obvious that there is a design flaw in the intended outcome of the ease of installation of these type of networks.