locked
Cannot join / login into Domain - Windows Server 2016 TP3 RRS feed

  • Question

  • I downloaded and installed the server 2016 TP3 (had to downloaded 3 times as the first 2 the size was around 2GB and not 4GB as it should). So after installing it and configuring DNS Server and Active Directory Domain Services all went fine.

    Now the problem is that I'm configuring a workstation to login into this domain, but not matter what I do I can not make the workstation see the domain and after going into COMPUTER --> PROPERTIES and selecting to change the COMPUTER from WORKGROUP to DOMAIN, it says that it cannot find any domain to join.

    Help would be appreciated. 

    Friday, October 9, 2015 5:15 AM

Answers

  • Make sure the domain controller is not multi-homed, both server and client have server's own address as primary DNS address on network connection properties. No public or router addresses.

    Clients should have local DNS address only so client can find and logon to domain. Forwarders are so clients can find and resolve internet queries.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, October 9, 2015 4:05 PM
  • Dave, I appreciate you taking the time to help me, that was exactly the problem, after changing the DNS from obtaining a DNS automatically to the IP of the AD DS DNS's IP address all the workstation's computers joined the domain without any issues.

    The DNS 192.168.0.1 is the IP of the Router.

    I had a vague idea it was DNS related but never imagine where the solution was. 

    I'm doing this as a project and the Windows Server 2016 has great possibilities.

    Once again thanks for your help.

    cheers!

    Friday, October 9, 2015 11:52 PM

All replies

  • If you connect to a computer running Windows Server 2016 Technical Preview and have a configuration to allow multiple simultaneous sessions, you will encounter a dialog to choose an existing session instead of logging in to a new session. There is no workaround at this time.

     

    If you configure a Remote Desktop Gateway farm and export the settings as an XML file, the Remote Desktop Gateway Management console on a subsequent server in the farm will not import the settings file. To work around this, manually replicates the settings on the second server.

    Friday, October 9, 2015 5:36 AM
  • I'm not referring to connecting to a new session to the Windows Server 2016, what I am talking about is login to a domain as a regular user from a regular computer that runs Windows 10, like a regular corporate employee that turns his computer and logs into the corporate domain.

    In order to login into the domain, one has to configure the computer not to use the general WORKGROUP but to use the Domain, ... When I try to configure that computer running Windows 10 to login to a domain by right-clicking in windows explorer the 'My Computer" or in this case "This PC" and selecting ""Properties" and then clicking on "Change" and on the window that opens up selecting the Radio button to login into a Domain, inputting the name of the domain and clicking on OK the window that pops up says that it could not find any domain by that name.

    I have to add up that I'm running Windows Server 2016 TP3 on a virtual machine on VMware Workstation 12 PRO, but that shouldn't be an issue, as I can ping fine this server FROM the Windows 10 box.

    The name of the server is WINSRV2016-TP3, and I noticed one thing: when I ping from the Windows 10 box using : "Ping winsrv2016-tpe -4" I get a response

    but when I ping the whole name: "Ping winsrv2016-tp3.domainname.com" I get an error that cannot find host. 

    From inside the windows server 2016 I can ping fine with the domain name at the end of the name of the windows server.


    • Edited by rocketero Friday, October 9, 2015 5:03 PM
    Friday, October 9, 2015 3:59 PM
  • Make sure the domain controller is not multi-homed, both server and client have server's own address as primary DNS address on network connection properties. No public or router addresses.

    Clients should have local DNS address only so client can find and logon to domain. Forwarders are so clients can find and resolve internet queries.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, October 9, 2015 4:05 PM
  • it's not a multi-homed controller, it has only one network card to connect to the home-network.

    I tried with another PC running Windows 8.1 and the same problem, it doesn't see the domain, and this computer connects fine to the regular not-domain network.

    I am just wondering if there is an issue with the DNS Server that holds the domain for the AD DS ? (I installed it following the step by step guideline from Microsoft technet website for installing AD DS on a Windows Server 2012R2 which is practically the same for Windows Server 2016 TP3

    • Proposed as answer by Aravind-CA Thursday, February 16, 2017 7:55 AM
    Friday, October 9, 2015 5:47 PM
  • Please post an unedited ipconfig /all of DC/DNS server and problem client.

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, October 9, 2015 5:52 PM
  • Configuración IP de Windows
    
       Nombre de host. . . . . . . . . : Win81X64ESP
       Sufijo DNS principal  . . . . . : 
       Tipo de nodo. . . . . . . . . . : mixto
       Enrutamiento IP habilitado. . . : no
       Proxy WINS habilitado . . . . . : no
       Lista de búsqueda de sufijos DNS: hsd1.ma.comcast.net.
    
    Adaptador de LAN inalámbrica Conexión de  rea local* 2:
    
       Estado de los medios. . . . . . . . . . . : medios desconectados
       Sufijo DNS específico para la conexión. . : 
       Descripción . . . . . . . . . . . . . . . : Adaptador virtual directo Wi-Fi de Microsoft
       Dirección física. . . . . . . . . . . . . : 12-68-9D-16-FA-AB
       DHCP habilitado . . . . . . . . . . . . . : s¡
       Configuración automática habilitada . . . : s¡
    
    Adaptador de Ethernet:
    
       Estado de los medios. . . . . . . . . . . : medios desconectados
       Sufijo DNS específico para la conexión. . : 
       Descripción . . . . . . . . . . . . . . . : Controladora Realtek PCIe GBE Family
       Dirección física. . . . . . . . . . . . . : 08-9E-01-3D-A4-7E
       DHCP habilitado . . . . . . . . . . . . . : s¡
       Configuración automática habilitada . . . : s¡
    
    Adaptador de LAN inalámbrica Wi-Fi:
    
       Sufijo DNS específico para la conexión. . : hsd1.ma.comcast.net.
       Descripción . . . . . . . . . . . . . . . : Adaptador de red inalámbrica Qualcomm Atheros AR5B125
       Dirección física. . . . . . . . . . . . . : 20-68-9D-16-FA-AB
       DHCP habilitado . . . . . . . . . . . . . : s¡
       configuración automática habilitada . . . : s¡
       Vínculo: dirección IPv6 local. . . : fe80::e940:4b5d:69b9:1946%3(Preferido) 
       Dirección IPv4. . . . . . . . . . . . . . : 192.168.0.109(Preferido) 
       Mascara de subred . . . . . . . . . . . . : 255.255.255.0
       Concesión obtenida. . . . . . . . . . . . : viernes, 9 de octubre de 2015 3:38:32
       La concesión expira . . . . . . . . . . . : viernes, 16 de octubre de 2015 3:38:17
       Puerta de enlace predeterminada . . . . . : 192.168.0.1
       Servidor DHCP . . . . . . . . . . . . . . : 192.168.0.1
       IAID DHCPv6 . . . . . . . . . . . . . . . : 52455581
       DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-1A-A8-21-A3-08-9E-01-3D-A4-7E
       Servidores DNS. . . . . . . . . . . . . . : 192.168.0.1
       NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitado
    
    Adaptador de túnel Teredo Tunneling Pseudo-Interface:
    
       Sufijo DNS específico para la conexión. . : 
       Descripción . . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Dirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP habilitado . . . . . . . . . . . . . : no
       configuración automática habilitada . . . : s¡
       Dirección IPv6 . . . . . . . . . . : 2001:0:9d38:6abd:831:1111:3f57:ff92(Preferido) 
       Vínculo: dirección IPv6 local. . . : fe80::831:1111:3f57:ff92%7(Preferido) 
       Puerta de enlace predeterminada . . . . . : ::
       IAID DHCPv6 . . . . . . . . . . . . . . . : 318767104
       DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-1A-A8-21-A3-08-9E-01-3D-A4-7E
       NetBIOS sobre TCP/IP. . . . . . . . . . . : deshabilitado
    
    Adaptador de túnel isatap.hsd1.ma.comcast.net.:
    
       Estado de los medios. . . . . . . . . . . : medios desconectados
       Sufijo DNS específico para la conexión. . : hsd1.ma.comcast.net.
       Descripción . . . . . . . . . . . . . . . : Adaptador ISATAP de Microsoft #2
       Dirección física. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP habilitado . . . . . . . . . . . . . : no
       configuración automática habilitada . . . : s¡
    



    • Edited by rocketero Friday, October 9, 2015 9:32 PM
    Friday, October 9, 2015 9:19 PM
  • The PREVIOUS WAS FOR THE WINDOWS 8.1 STATION (The workstation is in SPANISH).   THE FOLLOWING: is the IPCONFIG for the WINDOWS SERVER  2016: (THE DOMAIN NAME FOR THE AD DS IS SAMREST.COM)

    C:\Windows\system32>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : WINSRV2016-TP3
       Primary Dns Suffix  . . . . . . . : samrest.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : samrest.com
    
    Ethernet adapter Ethernet0:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
       Physical Address. . . . . . . . . : 00-0C-29-69-2C-B2
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d51f:ebc:6633:233b%3(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.108(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 50334761
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-A8-C0-A2-00-0C-29-69-2C-B2
       DNS Servers . . . . . . . . . . . : ::1
                                           192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter Local Area Connection* 1:
    
       Media State . . . . . . . . . . . : Media disconnected
       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
    
    Tunnel adapter isatap.{1762AB33-AFA2-46EC-BA07-7F0D79F5A505}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes




    • Edited by rocketero Friday, October 9, 2015 9:36 PM
    Friday, October 9, 2015 9:22 PM
  • This is the IPCONFIG FOR THE WINDOWS 8.1 STATION. The station is in SPANISH language but it's easy to see the outpu

    C:\Windows\system32>ipconfig /all

    Configuraci¢n IP de Windows

       Nombre de host. . . . . . . . . : Win81X64ESP
       Sufijo DNS principal  . . . . . : 
       Tipo de nodo. . . . . . . . . . : mixto
       Enrutamiento IP habilitado. . . : no
       Proxy WINS habilitado . . . . . : no
       Lista de b£squeda de sufijos DNS: hsd1.ma.comcast.net.

    Adaptador de LAN inal mbrica Conexi¢n de  rea local* 2:

       Estado de los medios. . . . . . . . . . . : medios desconectados
       Sufijo DNS espec¡fico para la conexi¢n. . : 
       Descripci¢n . . . . . . . . . . . . . . . : Adaptador virtual directo Wi-Fi de Microsoft
       Direcci¢n f¡sica. . . . . . . . . . . . . : 12-68-9D-16-FA-AB
       DHCP habilitado . . . . . . . . . . . . . : s¡
       Configuraci¢n autom tica habilitada . . . : s¡

    Adaptador de Ethernet Ethernet:

       Estado de los medios. . . . . . . . . . . : medios desconectados
       Sufijo DNS espec¡fico para la conexi¢n. . : 
       Descripci¢n . . . . . . . . . . . . . . . : Controladora Realtek PCIe GBE Family
       Direcci¢n f¡sica. . . . . . . . . . . . . : 08-9E-01-3D-A4-7E
       DHCP habilitado . . . . . . . . . . . . . : s¡
       Configuraci¢n autom tica habilitada . . . : s¡

    Adaptador de LAN inal mbrica Wi-Fi:

       Sufijo DNS espec¡fico para la conexi¢n. . : hsd1.ma.comcast.net.
       Descripci¢n . . . . . . . . . . . . . . . : Adaptador de red inal mbrica Qualcomm Atheros AR5B125
       Direcci¢n f¡sica. . . . . . . . . . . . . : 20-68-9D-16-FA-AB
       DHCP habilitado . . . . . . . . . . . . . : s¡
       Configuraci¢n autom tica habilitada . . . : s¡
       V¡nculo: direcci¢n IPv6 local. . . : fe80::e940:4b5d:69b9:1946%3(Preferido) 
       Direcci¢n IPv4. . . . . . . . . . . . . . : 192.168.0.109(Preferido) 
       M scara de subred . . . . . . . . . . . . : 255.255.255.0
       Concesi¢n obtenida. . . . . . . . . . . . : viernes, 9 de octubre de 2015 3:38:32
       La concesi¢n expira . . . . . . . . . . . : viernes, 16 de octubre de 2015 3:38:17
       Puerta de enlace predeterminada . . . . . : 192.168.0.1
       Servidor DHCP . . . . . . . . . . . . . . : 192.168.0.1
       IAID DHCPv6 . . . . . . . . . . . . . . . : 52455581
       DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-1A-A8-21-A3-08-9E-01-3D-A4-7E
       Servidores DNS. . . . . . . . . . . . . . : 192.168.0.1
       NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitado

    Adaptador de t£nel Teredo Tunneling Pseudo-Interface:

       Sufijo DNS espec¡fico para la conexi¢n. . : 
       Descripci¢n . . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Direcci¢n f¡sica. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP habilitado . . . . . . . . . . . . . : no
       Configuraci¢n autom tica habilitada . . . : s¡
       Direcci¢n IPv6 . . . . . . . . . . : 2001:0:9d38:6abd:831:1111:3f57:ff92(Preferido) 
       V¡nculo: direcci¢n IPv6 local. . . : fe80::831:1111:3f57:ff92%7(Preferido) 
       Puerta de enlace predeterminada . . . . . : ::
       IAID DHCPv6 . . . . . . . . . . . . . . . : 318767104
       DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-1A-A8-21-A3-08-9E-01-3D-A4-7E
       NetBIOS sobre TCP/IP. . . . . . . . . . . : deshabilitado

    Adaptador de t£nel isatap.hsd1.ma.comcast.net.:

       Estado de los medios. . . . . . . . . . . : medios desconectados
       Sufijo DNS espec¡fico para la conexi¢n. . : hsd1.ma.comcast.net.
       Descripci¢n . . . . . . . . . . . . . . . : Adaptador ISATAP de Microsoft #2
       Direcci¢n f¡sica. . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP habilitado . . . . . . . . . . . . . : no
       Configuraci¢n autom tica habilitada . . . : s¡

    Servidores DNS. . . . . . . . . . . . . . : 192.168.0.1

    This needs to be the address of the ADDNS server

    If you're going to use router for DHCP that's OK but you'll need to change the DNS address that it hands out. (also cannot have public or others as secondary)

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, October 9, 2015 9:23 PM
  • And this is the IPCONFIG for the Webserver 2016:

    C:\Windows\system32>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : WINSRV2016-TP3
       Primary Dns Suffix  . . . . . . . : samrest.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : samrest.com
    
    Ethernet adapter Ethernet0:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
       Physical Address. . . . . . . . . : 00-0C-29-69-2C-B2
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d51f:ebc:6633:233b%3(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.108(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 50334761
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-A8-C0-A2-00-0C-29-69-2C-B2
       DNS Servers . . . . . . . . . . . : ::1
                                           192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter Local Area Connection* 1:
    
       Media State . . . . . . . . . . . : Media disconnected
       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
    
    Tunnel adapter isatap.{1762AB33-AFA2-46EC-BA07-7F0D79F5A505}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

        DNS Servers . . . . . . . . . . . : ::1
                                           192.168.0.1

    Remove the router address and replace with server's own address. 192.168.0.108 for primary use 127.0.0.1 for secondary

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, October 9, 2015 9:28 PM
  • Dave, I appreciate you taking the time to help me, that was exactly the problem, after changing the DNS from obtaining a DNS automatically to the IP of the AD DS DNS's IP address all the workstation's computers joined the domain without any issues.

    The DNS 192.168.0.1 is the IP of the Router.

    I had a vague idea it was DNS related but never imagine where the solution was. 

    I'm doing this as a project and the Windows Server 2016 has great possibilities.

    Once again thanks for your help.

    cheers!

    Friday, October 9, 2015 11:52 PM
  • Good to hear, you're welcome.

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, October 10, 2015 12:17 AM
  • Hello,

    I use to have the same issue with our infrastructure where with our 5 DC ,a server on which I installed windows server 2016 and a workstation on which windows 10 is installed it can`t be added on a domain.

    The error message says "Network path was not found",I tried multiple times and failed.

    In addition to that the shared Folder we use to have in our Infrastructure which were running on windows server 2008 R2 and windows server 2012 R2 were all not be able to be mapped to end users workstations.

    Can you please advise the way forward?All steps indicated above were followed but there is no success.

    Kindly advise the right solution for this issue.

    Thanking you

    Tuesday, September 11, 2018 12:14 PM