There are currently no logon servers available to service the logon request Server 2012 DC (physical) + Terminal server 2012 (virtual)

I have an HP server running Server 2012 as a DC (phyiscal) with an additional virtual Server 2012 running as a Terminal Server. The virtual Server claims at random that there are currently no logon servers available to service the logon request and denies all users access. I can however log on to the virtual Server via the Hyper V console as any user without issue and even take over any of the users sessions? The issue presents randomly without warning and can happen 2/3 times a day. A reboot of the Terminal Server however, fixes the problem until the next occurance. The error logs just show "This computer was not able to set up a secure session with a domain controller in domain **** due to the following: There are currently no logon servers available to service the logon request." I have already tried removing the Virtual Server from the Domain and re-adding it but to no avail. Any help would be greatly appreciated.
ProtecUKAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
due to the following: There are currently no logon servers available to service the logon request
This is a classic message specifically related to DNS.

Now you may check your DNS settings on your network adapters on this server and they may look correct. However, if you have DC's that have not been properly removed from the domain and they are present in the SRV locations under the _msdcs.domain.com folder in the DNS console this could be exactly why you are running into this.

The way DNS works when you have these entries on your network adapter does not mean Primary is the only DNS server used for services. It is the primary DNS server you first reference to get DNS info. It then points you to the SRV records which contain all of the DNS/DC servers which will the auto select one of those servers for availability services.

When it references these records it is random so if you have bad entries in here this is where i can create issues.

So i would check your SRV records in DNS and also make sure that you do not have any DC's that have not been properly removed.

Another common reason for this is if it machine has lost its trust with the domain. You can verify this very easily using the following command...
netdom verify <computername> /Domain:domain.com /UserO:administrator /PasswordO:* <press enter>
Type Password:

Open in new window


The * in the /PasswordO: hides your password characters.

Will.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ProtecUKAuthor Commented:
Hi Will,

Thank you for your assistance and for your prompt response, it is really appreciated.

I have checked the SRV records in the DNS as you suggested and could not find an issue.

I have also removed the virtual server from the domain, rebooted it then rejoined it to the domain just incase their was an issue with the virtual server losing trust with the domain.

The actual secreen message that is presented to remote users when they try to logon is: "The specified domain either does not exsist or could not be contacted"Screen Capture
Any further users are then presented with the same message.

However I can log in as any user despite this message via the Hyper V manager on the DC.

Rebooting the virtual server immediately resolves the issue but only for a few hours..

Any further suggestions would be greatly welcomed.

Kind regards,

Glenn
Will SzymkowskiSenior Solution ArchitectCommented:
Is this the only machine that is doing this? How is the machine sys-prepped ? Do you have another server on the domain that is using the same name or IP address? In DNS is this machine registered properly?

Also when users are encountering this, what do the event logs state? Check system and application.

Will.
ProtecUKAuthor Commented:
Hi Will,

It appears that you were correct first time round. The server was built and configured on a network with another domain already configured pre-deployment. The new server had seen the DC that was on the network and added it to the DNS. Once removed the problem cleared.

Thank you so much for your time and input. I simply missed the first time around..

Kind regards,

glenn
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.