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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
Also when users are encountering this, what do the event logs state? Check system and application.
Will.
ASKER
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 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
ASKER
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"
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