none
When joining domain, there says the specified network name is no longer available RRS feed

  • Question

  • Hi guys,


    I met a strange issue. When a server joining domain, there shows the following error occurred attempting to join the domain, the specified network name is no longer available.


    The domain controller and the client server are all windows 2012 R2 and in different location.

    I have tested dns with nslookup and looks fine.

    Ports UDP 53 88 138 working, TCP 53 88 389 445 636 working.

    UDP 137 can't be connected. But this didn't seem to be the cause.


    Any suggestions?

    Thanks in advance.
    Friday, November 25, 2016 6:26 AM

All replies

  • Hi

     Please run "ipconfig /all" both DC and client then share the results.


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Friday, November 25, 2016 6:30 AM
  • The client,

    PS C:\Users\Administrator> ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : b
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Ethernet 2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
       Physical Address. . . . . . . . . : 00-50-56-94-39-CA
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.107.100.219(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.107.100.1
       DNS Servers . . . . . . . . . . . : 10.119.12.110
                                           10.119.12.111
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{B1F33897-E833-4F20-AB08-914A32DAA193}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:3cc8:14da:2db5:7cad(Preferred)
       Link-local IPv6 Address . . . . . : fe80::3cc8:14da:2db5:7cad%14(Preferred)
       Default Gateway . . . . . . . . . : ::
       DHCPv6 IAID . . . . . . . . . . . : 385875968
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-5A-9D-DC-00-50-56-94-39-CA
       NetBIOS over Tcpip. . . . . . . . : Disabled

    The DC,

    PS C:\Users\aaa> ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : a
       Primary Dns Suffix  . . . . . . . : domain.root
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : domain.root

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Cisco VIC Ethernet Interface
       Physical Address. . . . . . . . . : 00-25-B5-1A-00-EF
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.119.12.110(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.119.12.1
       DNS Servers . . . . . . . . . . . : 10.119.12.111
                                           127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Friday, November 25, 2016 6:39 AM
  • BTW, I can't ping the DC with it's server name on the client, only can ping it with the full domain name a.domain.root.
    Friday, November 25, 2016 6:47 AM
  • IPv4 Address. . . . . . . . . . . : 10.107.100.219(Preferred)
    DNS Servers . . . . . . . . . . . : 10.119.12.110
                                        10.119.12.111
    IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:3cc8:14da:2db5:7cad(Preferred)>>> You should disable this second nic on dc.

    DC dns settings should be fix,dns ip needs to be point to itself.
    DNS Servers . . . . . . . . . . . : 10.119.12.111 >> when you fix dc dns ip address then you should configure dc ip address.

    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Friday, November 25, 2016 6:48 AM
  • Hi Burak,

    Thanks for your quick replay. I have updated the settings but the issue still there. Also tried created a computer account in the domain, doesn't work either.

    Friday, November 25, 2016 7:02 AM
  • when you fix dns ip on dc then run "ipconfig /flushdns" and "ipconfig /registerdns"..finaly try again..if issue still occours you can check the connection with Microsoft Network Monitor 3.4(to analyze the source);

    https://www.microsoft.com/en-us/download/details.aspx?id=4865


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Friday, November 25, 2016 7:18 AM
  • Hi,

    I am checking how the issue going, if you still have any questions, please feel free to contact us.

    And if the replies as above are helpful, we would appreciate you to mark them as answers, and if you resolve it using your own solution, please share your experience and solution here. It will be greatly helpful to others who have the same question.

    Appreciate for your feedback.

    Best regards,

    Wendy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, November 29, 2016 4:02 AM
    Moderator
  • I was getting this on a server with 2 network cards (NICs). I disabled 1 NIC and domain joining worked fine.
    Friday, August 17, 2018 9:49 AM