Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


The dreaded  "The specified domain either does not exist or could not be contacted" error

Posted on 2015-01-19
Medium Priority
Last Modified: 2015-02-02
Here's the scenario.

Host machine running Windows 2012 Server R2, all updates installed. Workgroup. Hyper-V installed.

1st Hyper-V machine

Windows 2012 R2 Server. Set as domain controller.
Roles installed
Active Directory Domain Services
DNS Server
File and Storage Services.

System is the DC and hosts user files. Also hosts Quickbooks data file.

2nd Hyper-V machine
Windows Server 2012R2 All updates installed.

Roles  installed
Remote Desktop Services
File and Storage services
Web Server (IIS)

Increasingly when user attempt to log into the TServer they'll get the  "The specified domain either does not exist or could not be contacted". error. Restarting DNS services on the DC and Tserver seems to resolve the issue temporarily. Ultimately the issue seems to self heal but not after disallowing log on for an unreasonable amount of time. 15 minutes or more. The issue has been occurring with greater frequency.

I'm not a DNS guru. The only resolutions I've found online to this point pertain to Server 2000 and 2003. Not much regarding this issue in 2012R2.

Thank you
Question by:gulfcoastnetworking
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
  • 4
  • 3
  • 2
LVL 53

Expert Comment

by:Will Szymkowski
ID: 40558196
When this issue happens have you tried to check the secure channel of the Terminal Server?
netdom verify <machinename> /Domain:yourdomain.com /UserO:username /PasswordO:*

"the * will allow you to enter the password once you press enter and characters are not shown on screen.

Verify the trust of the machine when the issue happens.

Also another good thing to check would be errors/warnings in the Event viewer on the Terminal server itself.


Author Comment

ID: 40558317
Thanks I will try that when the issue arises. I'd run a DCDIAG  /test:DNS test in the past and it passed.

The most recent error on the TS was 5719 NETLOGON source, Essentially saying the machine was not able to setup a secure session with the domain controller in domain "abc" due to the following. No Logon servers were available to service the logon request.

Checking the DC I found no errors that indicated it not being available around the time stamp of the TS error.
LVL 53

Expert Comment

by:Will Szymkowski
ID: 40558402
Netlogon services need to be running in order to login to the domain successfully. If this service is having issues and it is stopping / restarting randomly this could be the issue to your probelm.

As you have already pointed out you have errors in the event log regarding the netlogon service as well.

I would start there.

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

LVL 25

Expert Comment

by:Lionel MM
ID: 40559518
What are the ipconfig setting of your clients--are there DNS servers just the DC or also those of their ISP? If ISP too try removing those and see if that resolves the issue.

Accepted Solution

gulfcoastnetworking earned 0 total points
ID: 40560262
Thanks lionelmm, I removed the reference to outside DNS from both the DC and the TS yesterday. Most clients are connecting from outside the facility so DNS of their machines should be irrelevant. There was also a service related to an old piece of monitoring software that was still running. I disabled that as well.

So far the issue has not reappeared, at least they haven't called to complain. Unfortunately I won't know if either of those were the issue for a couple of days. Generally the issue appears at least once a day. definitely a number of times per week.

Fingers crossed.
LVL 25

Expert Comment

by:Lionel MM
ID: 40560709
Most clients are connecting from outside the facility so DNS of their machines should be irrelevant.
It has been my experience that many times client systems cannot join to a domain (domain server not found) or that it takes a VERY long time to find the DC if client PCs have DNS servers other than the domain DNS they wish to connect to--thus my suggestion may be worthwhile trying if the issue re-appears on some systems
LVL 25

Expert Comment

by:Lionel MM
ID: 40575292
but you have not given credit--you have chosen to delete giving only credit to your final comment--I assume you did this by mistake?

Author Closing Comment

ID: 40583589
I'm giving credit for this solution because it was at least partially the ultimate solution. Thank you.
LVL 25

Expert Comment

by:Lionel MM
ID: 40583744
but you are only giving credit to your own comments and to none of the others, in affect awarding 0 point to yourself only--is this what you want to do?

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

INTRODUCTION The purpose of this document is to demonstrate the Installation and configuration of the Data Protection Manager product. Note that this demonstration was prepared on the basis of Windows OS is 2008 R2 and DPM 2010. DATA PROTECTI…
Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Suggested Courses

610 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