Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cannot get XP Pro to join a 2000 ADC (domain)

Status
Not open for further replies.

abqtech

Technical User
Apr 13, 2003
3
US
When I try to connect a win XP Pro workstation to a Win 2K Server running Active Directory, I get the following error:

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:
(the root zone)

The XP workstation is able to recieve an IP address from the win2k Server, and is also able to proxy through it.
There are several other workstations on this network, that were able to join the domain without this problem.

The XP workstation is not running any kind of firewall. I can ping the server by IP from this workstation, and from the server I can ping the XP workstation by IP.

The XP workstation is configured to use Netbios via DHCP.

The XP workstion does get an IP Address, Gateway, Subnet Mask, WINS, & DNS from this win2k server...

It just seems that the XP workstation cannot browse netbios names.

Any Ideas? Thanks!
 
Is the server auto-assigning everything? I had a similar problem, but I manually assign (small network, lets me do it) IP and DNS. one thing you MIGHT want to try is manually assign the DNS, just have it point to the domain servers' IP address, see if that helps. Turned out with mine I had forgotten to change the domain server from the old 2K server box to the new one, and then it worked fine.
 
thanks for the reply... it turns out that the workstation was part of a different network at one point, and it was configured to use a Micro$oft Proxy (either 2.0 or ISA) firewall client. By installing the ISA 2000 firewall client the issue was resolved.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top