windows 2003 server : can't join domain

Posted by phill on Server Fault See other posts from Server Fault or by phill
Published on 2010-04-11T23:05:21Z Indexed on 2010/04/11 23:43 UTC
Read the original article Hit count: 483

Filed under:
|

I originally tried to rejoin a computer to a network which led to a "cannot find domain" error. The username/password box don't even come up.

some tests i ran: I can ping the server, however I can't ping the domain name domain1.local.
nslookup can't find the domain either. It looks to the isp's dns instead of my own to resolve the local machines.

So i go to the dns and run netdiag.exe and gives me this error.

DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'stmartinsrv.stmartin.local.'. [RCODE_SERVER_FAILURE]
            The name 'srv.domain1.local.' may not be registered in DNS.

    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '68.94.156.1'. Please wait for 30 minutes for DNS server replication.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '68.94.157.1'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{04BB0F6B-06AE-4D60-80C8-2A7A24C1D87B}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{04BB0F6B-06AE-4D60-80C8-2A7A24C1D87B}
    The browser is bound to 1 NetBt transport.

then running dcdiag

C:\Program Files\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup: Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SRV Starting test: Connectivity The host 1c99f63c-49ec-40db-b3d3-6265c00fbd3e._msdcs.domain1.local cou ld not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (1c99f63c-49ec-40db-b3d3-6265c00fbd3e._msdcs.domain1.local) couldn't be resolved, the server name (srv.domain1.local) resolved to the IP address (192.168.1.21) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... SRV failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\SRV
      Skipping all tests, because server SRV is
      not responding to directory service requests

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : domain1
      Starting test: CrossRefValidation
         ......................... domain1 passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... domain1 passed test CheckSDRefDom

   Running enterprise tests on : domain1.local
      Starting test: Intersite
         ......................... domain1.local passed test Intersite
      Starting test: FsmoCheck
         ......................... domain1.local passed test FsmoCheck

from previous postings, I've tried adding the domain suffix to the nic ip properties to both the client machine and the dc server which didn't help.

note: there is only one nic on the server

any ideas? thanks in advance

© Server Fault or respective owner

Related posts about windows-server-2003

Related posts about dns