[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


W 10 Workstation can't join Win 2012 domain

Posted on 2016-11-22
Medium Priority
Last Modified: 2017-02-02
Everything was working normally till I replaced a router. Windows 2012 R2 server (AD, DNS, DHCP) local domain. I installed the new router and forgot to turn off DHCP in the router. A windows 10 workstation started having problems connecting to a server based application. I found the mistake by using ipconfig, and turned off DHCP in the router. Workstation still won't connect. All mapped drives are disconnected. The network profile changed to "Private" and was disabled. I used powershell to change it to "public" but it is still disabled. I tried dis-joining the workstation from the domain and tried to rejoin. Error message is "An Active Directory Domain Controller (AD DC) for the domain could not be contacted". I can ping from the workstation to the DC and from the DC to the workstation by IP and name. Workstation A record is in DNS. I have tried turning off the windows firewall, ipconfig /flushdns, tried a static IP on the workstation, restart netlogon, restart server and workstation, verified discovery and file sharing are enabled. no luck yet. any ideas would be welcome.
Question by:rettif9
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 8
  • 3
LVL 41

Expert Comment

ID: 41898399
If the adapter is still disabled, it won't be able to communicate.
Try getting a new lease from your DHCP.
ipconfig /release
ipconfig /renew

It should only be using your internal DNS, so double check the output of ipconfig /all.

Author Comment

ID: 41898403
No I'm accessing the workstation off-site so I haven't disabled/enabled the NIC although I would like to. I already checked ipconfig.
IP was in the scope, gateway was correct and DHCP and DNS were the DC's IP.

Assisted Solution

by:Raul Ivan Medina Urista
Raul Ivan Medina Urista earned 600 total points
ID: 41898418
Clear router’s entire ARP cache. Delete all the IP leases  except reservations and restart the DHCP service.

Raúl Medina.
Q2 2017 - Latest Malware & Internet Attacks

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out our latest Quarterly Internet Security Report!


Author Comment

ID: 41898436
Thanks Raúl Medina,

I tried your idea but I still get the same error when I try to join the workstation to the domain.
LVL 41

Expert Comment

ID: 41898438
So you can ping the DC by name?
What's the result of running nltest /dsgetdc:yourdomain ?

A domain-joined workstation that is connected to the domain network should show the profile as "domain" (you can't force this).  Depending on Group Policy settings different profiles could allow different traffic, but usually all outbound traffic is allowed, but you may want to check this.
Where is the server-based application?  How do you connect to it?

Edit:  From your last comment, you did unjoin it, but just can't re-join it to the domain.  Are you using the NetBIOS name or DNS name of the domain?

Author Comment

ID: 41898444
Thanks Footech here is the info you asked for,

Yes I know I couldn't force the profile to change to domain. Because "Private " was inactive (not blue) I changed it to "Public" just to see if it would be active. I'm logged onto the workstation currently as a local administrator account;
C:\Users\admin>nltest /dsgetdc:yourdomain
Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
also tried: nltest /dsgetdc:[domain_name] - same result

C:\Users\admin> ping CCSCDC1

Pinging ccscdc1.[domain_name].local [] with 32 bytes of data:
Reply from bytes=32 time=1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128

The application is a hybrid cloud application. Some data is on the local app server. some is at the vendors site.
Just FYI
workstation IP is (dhcp)

Author Comment

ID: 41898456
I was looking up syntax on command as I'm not familiar with it and found this. Not sure if it is useful information. https://www.experts-exchange.com/questions/28579078/nslookup-dsgetdc-Getting-DC-name-failed-Status-1355-0x54b-ERROR-NO-SUCH-DOMAIN.html
 I am substituting the actual domain name with [domain_name]

C:\Users\admin>nslookup /dsgetdc:[domain_name].local
Server:  ccscdc1.[domain_name].local

*** ccscdc1.[domain_name].local can't find /dsgetdc:[domain_name].local: Non-existent domain
LVL 41

Accepted Solution

footech earned 1400 total points
ID: 41898462
/dsgetdc is a switch for the nltest.exe utility, not nslookup.

Are you using the NetBIOS name or DNS name of the domain when trying to join?  Best practice is to always use the FQDN.
Here's the common causes I can think of (or heard mentioned) for problems joining a domain:
 - SRV records incorrect
 - workstation IP configuration incorrect - either DNS, subnet, etc.  If IPv6 info is incorrect, just unbinding it from the adapter seems to be the quickest fix.
 - having network profile set to Public

Author Comment

ID: 41898469
using [domain_name].local to join domain.

Since DNS was working without any issues and hasn't been changed it seems safe to assume it is correct.

IP config is;
 IPv4 Address. . . . . . . . . . . :
   Subnet Mask . . . . . . . . . . . :
   Lease Obtained. . . . . . . . . . : Tuesday, November 22, 2016 5:44:44 PM
   Lease Expires . . . . . . . . . . : Wednesday, November 30, 2016 5:44:43 PM
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 246991418
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-1F-82-0F-B8-CA-3A-85-28-7C
   DNS Servers . . . . . . . . . . . :

I'll try unbinding IPV6

Author Comment

ID: 41898491
Thanks Footech for the suggestions,

I disabled IPV6 and rebooted. Same error occurred.

Author Comment

ID: 41898553
This problem was misleading. I had a VPN tunnel down and didn't know it. This DC couldn't contact the PDC emulator. Once that was fixed the workstation problem went away.

Author Closing Comment

ID: 41898554
Thanks to both of you.

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question