Re: Cannot join domain...very odd

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

So you're trying to join those PC's to the domain?

Is DNS working correctly, for those 2 PC's? Can they ping the DC by host
name?
Usually, problems related to joining a domain are DNS related.
Did you try the fully qualified domain name, when adding it to the domain?



"MLT-TECH" <mlttech@xxxxxxx> wrote in message
news:ORStpQV2JHA.1644@xxxxxxxxxxxxxxxxxxxxxxx
Cannot join domain...very odd

I am trying to get two XP SP2 workstations to connect to a domain called
test.local. Their IP is 192.168.0.2 and 192.168.0.3 (static). Their
gateway is left blank and their DNS entered is the IP address of the
Domain Controller hosting the test.local domain being 192.168.0.1.....but
when I try to connect these workstations to this domain the below error is
being encountered:


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 following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
test.local:

The error was: "This operation returned because the timeout period
expired."
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.test.local

The DNS servers used by this computer for name resolution are not
responding. This computer is configured to use DNS servers with the
following IP addresses:

192.168.0.1

Verify that this computer is connected to the network, that these are the
correct DNS server IP addresses, and that at least one of the DNS servers
is running.

For more information on how to correct this problem, click Help.


In the past these two workstations were connected to a different domain
however at this moment they are set on a workgroup. These PCs don't have
any firewall software installed and other workstations can connect to the
domain without problems so the problem is related with these two
particular machines. Formatting the machines is not an option as they have
a lot of applications installed and data stored.

Your help is greatly appreciated.

regards




.

Relevant Pages

  • Re: sys vol check
    ... instead of the local DNS server and two ISP DNS servers. ... I need to configure the DHCP to use all three internal DNS servers ... If DNS zones are AD Integrated are writtable. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Which TCP/IP settings critical to join domain?
    ... the DCs are not configured with DNS. ... The workstations in the same subnet as the DCs were able to join the ... >>Our DCs can write SRV records to the backbone DNS servers, ...
    (microsoft.public.win2000.networking)
  • Re: DCs not responding to logon requests
    ... Each workstation has two DNS servers set, one is indeed for the server I am ... shutting off but the second is for one of the other DCs. ... >> Running DCDIAG and NETDIAG from the workstations aimed at the servers I ...
    (microsoft.public.windows.server.active_directory)
  • Re: sys vol check
    ... You've 3 DC DNS servers one in each Site with different subnets. ... You've A forward lookup Zone named CORP.DLECINC.COM and a reverse lookup ... The clients should use only their local DNSserver in ther NIC ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cannot join domain...very odd
    ... I am trying to get two XP SP2 workstations to connect to a domain called ... The following error occurred when DNS was queried for the service location ... The query was for the SRV record for _ldap._tcp.dc._msdcs.test.local ... The DNS servers used by this computer for name resolution are not ...
    (microsoft.public.windows.server.active_directory)