none
Join server 2003 domain with windows 10 RRS feed

  • Question

  • I have attempted to use the domain wizard built into windows 10 to join a windows server 2003 domain.  I have set up an account on the server for the new computer, and I have admin. access for the user.    I can enter the domain in the wizard, it requests a name and a password, it waits about 60 seconds,  then I get a message the domain cannot be found.  I have tried just the domain name and also domain name adding .local

    Saturday, August 8, 2015 4:22 PM

Answers

  • Ethernet adapter Ethernet:

       Media State . . . . . . . . . . . : Media disconnected

    Hi:  Can you please try with a wired connection?

     Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1

    That must be the ip of the router?

    But what are these?

    DNS Servers . . . . . . . . . . . : 209.18.47.61
                                           209.18.47.62
                                           192.168.1.1

    And what is the ip and subnet mask of the Server?


    Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

    Monday, August 31, 2015 9:26 PM
    Moderator

All replies

  • Hi:

    Plain Server 2003 or SBS 2003?


    Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

    Saturday, August 8, 2015 9:57 PM
    Moderator
  • Hi,

    I want to confirm with you that if you try to join Windows 10 to Windows Server 2003 domain with:
    System – Change settings – Computer name – Change – Domain.

    If so, on the client, confirm the configuration of preferred DNS server on TCP/IPv4 properties, make sure that this IP address is the DNS server which can locate the DC(including related SRV and A records).

    If there is any 3rd party software, disable it temporarily. Besides, check to see if the client can resolve domain name. 

    Open CMD on client, type the commend line below and end with enter(suppose that the domain name is domain.com):
    NSlookup domain.com

    If this command can successfully resolve the domain name and return DC’s IP address. Have you tried to confirm that if this problem only happened on Windows 10 client? if any other device can successfully join the domain?

    Best Regards,
    Eve Wang

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

    Monday, August 10, 2015 6:03 AM
    Moderator
  • When i tried to find my domain using the change settings-computer name-domain I get an answer "That domain couldn't be found"

    I tried the command you suggested, and it seems to find the domain:

    Microsoft Windows [Version 10.0.10240]
    (c) 2015 Microsoft Corporation. All rights reserved.
    C:\Users\Brian>NSlookup kiefer.local
    Server:  dns-cac-lb-01.rr.com
    Address:  209.18.47.61
    Non-authoritative answer:
    Name:    kiefer.local
    Addresses:  198.105.254.228
              198.105.244.228

    C:\Users\Brian>NSlookup kiefer
    Server:  dns-cac-lb-01.rr.com
    Address:  209.18.47.61
    Non-authoritative answer:
    Name:    kiefer
    Addresses:  198.105.254.228
              198.105.244.228

    C:\Users\Brian>

    I changed the DNS server address to the ones listed above in my network settings for the TCP/IPv4, still could not change domain.

    Wednesday, August 12, 2015 5:36 PM
  • Hi,

    If it is a newly upgraded Windows 10, please try to update the hardware drivers, such NIC. In general, Windows Update will provide the available driver update for your device, or, you may access the hardware/manufacture’s website to download and manually install the latest version of drivers.

    Besides, is problem only happened on Windows 10 client? Otherwise, you may run DCdiag on the DC to check the state:
    https://technet.microsoft.com/en-us/library/cc776854(v=ws.10).aspx 

    If the problem persists, please post the “ipconfig /all” result of Windows 10.

    Best Regards,
    Eve Wang

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

    Monday, August 17, 2015 11:33 AM
    Moderator
  • Microsoft Windows [Version 10.0.10240]
    (c) 2015 Microsoft Corporation. All rights reserved.
    C:\Users\Brian>ipconfig /all
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : BrianHPLaptop
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Ethernet:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 30-8D-99-C9-02-C9
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Wireless LAN adapter Local Area Connection* 3:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
       Physical Address. . . . . . . . . : 34-02-86-E7-E6-50
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Wireless LAN adapter Wi-Fi:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7265
       Physical Address. . . . . . . . . : 34-02-86-E7-E6-4F
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::eda9:79b2:3d7f:745b%7(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.143(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Monday, August 31, 2015 5:00:46 PM
       Lease Expires . . . . . . . . . . : Tuesday, September 1, 2015 5:00:50 PM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 104071814
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-10-A2-EB-30-8D-99-C9-02-C9
       DNS Servers . . . . . . . . . . . : 209.18.47.61
                                           209.18.47.62
                                           192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Bluetooth Network Connection:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
       Physical Address. . . . . . . . . : 34-02-86-E7-E6-53
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:74:31a1:bccb:cf75(Prefer
    red)
       Link-local IPv6 Address . . . . . : fe80::74:31a1:bccb:cf75%3(Preferred)
       Default Gateway . . . . . . . . . : ::
       DHCPv6 IAID . . . . . . . . . . . : 301989888
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-10-A2-EB-30-8D-99-C9-02-C9
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Tunnel adapter isatap.{1D85AECC-062E-4A9A-98E9-AF75A6057B63}:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    C:\Users\Brian>ip
    Monday, August 31, 2015 9:09 PM
  • Ethernet adapter Ethernet:

       Media State . . . . . . . . . . . : Media disconnected

    Hi:  Can you please try with a wired connection?

     Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1

    That must be the ip of the router?

    But what are these?

    DNS Servers . . . . . . . . . . . : 209.18.47.61
                                           209.18.47.62
                                           192.168.1.1

    And what is the ip and subnet mask of the Server?


    Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

    Monday, August 31, 2015 9:26 PM
    Moderator
  • I have been having this issue as well.

    I found that when doing an NSLookup, it returned IPV6 results. I assume that SBS2003 has an issue with IPV6, so I removed the tick from the IPV6 setting on the Ethernet properties on the Windows 10 machine, leaving just the IPV4 setting.

    I rebooted the machine and attempted to connect to the domain again.

    It connected immediately.

    Hope this helps.


    Brenton

    • Proposed as answer by dreadnorth Wednesday, February 8, 2017 2:28 PM
    Thursday, July 21, 2016 6:20 AM
  • I just stumbled across this and solved a problem I had been working on for 3 days. Thank you so much!
    Tuesday, March 28, 2017 2:40 PM
  • Your welcome.  This is why the forum is here, and why we post.

    Larry Struckmeyer [MVP]-- --If your question is answered please mark the response as the answer so that others can benefit.

    Wednesday, March 29, 2017 1:13 AM
    Moderator
  • we have had same trouble also. Simple resolve is:
    Turn on Computer,

    start CMD

    Ping to DomainController server f.E. c:\ping cybiad01

    it will last some seconds, then name is resolved, ping will be successful,

    Now you can bring the computer to the domain by changing is from homenet to DOMAIN, the domain will be resolved.

    Wednesday, May 17, 2017 9:12 AM
  • I have been having this issue as well.

    I found that when doing an NSLookup, it returned IPV6 results. I assume that SBS2003 has an issue with IPV6, so I removed the tick from the IPV6 setting on the Ethernet properties on the Windows 10 machine, leaving just the IPV4 setting.

    I rebooted the machine and attempted to connect to the domain again.

    It connected immediately.

    Hope this helps.


    Brenton

    I had the same issue, followed advice on various forums to no avail. Some telling you to change registry settings and use the offline djoin tool, all of which failed. The key bit of info here is disabling IPv6 and Rebooting !!. The reboot is key. I disabled IPv6 but didn;t reboot. Once I had rebooted my issue was resolved. 

    If in doubt when having issues with Windows, a reboot 99% of hte time fixes the issue.,. lol

    Monday, December 30, 2019 3:53 PM