none
Can't join AD Domain using FQDN - Fails with Error 53 "Network Path not Found"

    Question

  • 06/22/2014 08:28:20:209 NetpDoDomainJoin
    06/22/2014 08:28:20:209 NetpMachineValidToJoin: 'MDMSRV01'
    06/22/2014 08:28:20:209 OS Version: 6.1
    06/22/2014 08:28:20:209 Build number: 7601 (7601.win7sp1_gdr.140303-2144)
    06/22/2014 08:28:20:209 ServicePack: Service Pack 1
    06/22/2014 08:28:20:209 SKU: Windows Server 2008 R2 Enterprise
    06/22/2014 08:28:20:209 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
    06/22/2014 08:28:20:209 NetpGetLsaPrimaryDomain: status: 0x0
    06/22/2014 08:28:20:209 NetpMachineValidToJoin: status: 0x0
    06/22/2014 08:28:20:209 NetpJoinDomain
    06/22/2014 08:28:20:209 Machine: MDMSRV01
    06/22/2014 08:28:20:209 Domain: phamnet.int
    06/22/2014 08:28:20:209 MachineAccountOU: (NULL)
    06/22/2014 08:28:20:209 Account: phamnet.int\GlobalAdmin
    06/22/2014 08:28:20:209 Options: 0x27
    06/22/2014 08:28:20:209 NetpLoadParameters: loading registry parameters...
    06/22/2014 08:28:20:209 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
    06/22/2014 08:28:20:209 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
    06/22/2014 08:28:20:209 NetpLoadParameters: status: 0x2
    06/22/2014 08:28:20:209 NetpValidateName: checking to see if 'phamnet.int' is valid as type 3 name
    06/22/2014 08:28:20:318 NetpCheckDomainNameIsValid [ Exists ] for 'phamnet.int' returned 0x0
    06/22/2014 08:28:20:318 NetpValidateName: name 'phamnet.int' is valid for type 3
    06/22/2014 08:28:20:318 NetpDsGetDcName: trying to find DC in domain 'phamnet.int', flags: 0x40001010
    06/22/2014 08:28:20:427 NetpLoadParameters: loading registry parameters...
    06/22/2014 08:28:20:427 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
    06/22/2014 08:28:20:427 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
    06/22/2014 08:28:20:427 NetpLoadParameters: status: 0x2
    06/22/2014 08:28:20:427 NetpDsGetDcName: status of verifying DNS A record name resolution for 'DOMCON02.phamnet.int': 0x0
    06/22/2014 08:28:20:427 NetpDsGetDcName: found DC '\\DOMCON02.phamnet.int' in the specified domain
    06/22/2014 08:28:20:427 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
    06/22/2014 08:29:08:707 [000002e0] NetpGetLsaPrimaryDomain: status: 0x0
    06/22/2014 08:29:10:345 NetUseAdd to \\DOMCON02.phamnet.int\IPC$ returned 53
    06/22/2014 08:29:10:345 NetpJoinDomain: status of connecting to dc '\\DOMCON02.phamnet.int': 0x35
    06/22/2014 08:29:10:345 NetpJoinDomainOnDs: Function exits with status of: 0x35
    06/22/2014 08:29:10:345 NetpDoDomainJoin: status: 0x35

    So it looks like Windows Server 2012 is vry fussy with the DNS records. I had no issues joining machines to the domain until Server 2012 came along. Can someone help here? If triple checked the SRV records in the DNS and ive screwed around with DNS suffixes etc. 

    Saturday, June 21, 2014 10:39 PM

Answers

  • Monday, June 23, 2014 5:44 AM
  • Looks like you have DNS issues.  Check your client and make sure the dns server on the clisnts nic settings are pointing at a DC's dns server.

    Can you post and ipConfig /all of the client having troubles and a client that is working from the same site.


    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security, BS CSci
    2012, 2008, Vista, 2003, 2000 (Early Achiever), NT4
    Twitter @pbbergs http://blogs.dirteam.com/blogs/paulbergson
    Please no e-mails, any questions should be posted in the NewsGroup.
    This posting is provided AS IS with no warranties, and confers no rights.

    Monday, June 23, 2014 12:01 PM
    Moderator
  • is NSLOOKUP able to resolve your FQDN? (Do not use the nslookup command-line tool to test DNSSEC support for a zone. The nslookup tool uses an internal DNS client that is not DNSSEC-aware.)

    Have you flushed your DNSCache?

    In your DNS Server role on the DC have you ensured the Name server records are correct? Forwarders are correct? Root hints, advanced options, etc.

    in the NIC Settings is the DNS tab setup properly?

    Are you able to use the example below to get similar results?

    PS C:\> Resolve-DnsName finance.secure.contoso.com –type A -server dns1.contoso.com
    
    Name                                           Type   TTL   Section    IPAddress
    ----                                           ----   ---   -------    ---------
    finance.secure.contoso.com                     A      2848  Answer     192.168.0.200
    

    Tuesday, June 24, 2014 3:03 PM

All replies

  • Monday, June 23, 2014 5:44 AM
  • Looks like you have DNS issues.  Check your client and make sure the dns server on the clisnts nic settings are pointing at a DC's dns server.

    Can you post and ipConfig /all of the client having troubles and a client that is working from the same site.


    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security, BS CSci
    2012, 2008, Vista, 2003, 2000 (Early Achiever), NT4
    Twitter @pbbergs http://blogs.dirteam.com/blogs/paulbergson
    Please no e-mails, any questions should be posted in the NewsGroup.
    This posting is provided AS IS with no warranties, and confers no rights.

    Monday, June 23, 2014 12:01 PM
    Moderator
  • is NSLOOKUP able to resolve your FQDN? (Do not use the nslookup command-line tool to test DNSSEC support for a zone. The nslookup tool uses an internal DNS client that is not DNSSEC-aware.)

    Have you flushed your DNSCache?

    In your DNS Server role on the DC have you ensured the Name server records are correct? Forwarders are correct? Root hints, advanced options, etc.

    in the NIC Settings is the DNS tab setup properly?

    Are you able to use the example below to get similar results?

    PS C:\> Resolve-DnsName finance.secure.contoso.com –type A -server dns1.contoso.com
    
    Name                                           Type   TTL   Section    IPAddress
    ----                                           ----   ---   -------    ---------
    finance.secure.contoso.com                     A      2848  Answer     192.168.0.200
    

    Tuesday, June 24, 2014 3:03 PM