Windows server 2008 no logon server available

This behavior and error are specific only to DSRM. DSRM is intentionally invoked as part of the cloning process to safeguard the network and domain from duplicated domain controllers. For more information about how to configure and troubleshoot VDC together with details and step-by-step guidance, see Virtualized Domain Controller Technical Reference Level Skip to main content. If I disjoin the client and add it back to the domain, it works again until the subsequent reboot it seems.

Thanks for your help! Friday, October 31, PM. Troubleshooting steps: 1. Friday, November 7, AM. Look at DNS. Hello, Does the issue exist on all the domain clients or a specific client? Please refer to the troubleshooting steps: 1. As this problem only happens after the client is rebooted, please also check the following: 1. Tuesday, November 4, AM. I will try these steps out but the problem appears to have gone away. I have two test clients set up now and they both work fine.

One problem that might be related though, is that the clients don't appear to be registering in the DNS on the domain controller, even though the DC itself does, and one other system did. I have dynamic updates both secure and unsecure to see if that was a problem enabled. Tuesday, November 4, PM. Hi, Thanks for the reply. Thursday, November 6, AM. Firewall is also disabled for all clients.

Primary DNS suffix is the same on server and client. Do you think the problem might be in the group policy overriding the DHCP? Manually adding an A record in the forward lookup zone will fix being able to right click and 'manage' a computer through Active Directory.

Also, I can ping the machine just by hostname and the name somehow resolves. I'm not running WINS. Thursday, November 6, PM. Is it not obeying this? So accordingly you need to troubleshoot. The only issue that network resources are not accessible in this case. I know that you certainly know its solution by rejoin to domain. But that is time taking and complex solution like remove from domain and reboot and then rejoin. Firstly, you need to verify the secure channel status between workstation and primary domain controller.

This post from MiniTool introduces some feasible methods for you. When you try to log in to a Windows Active Directory domain, the client user receives the following Windows error message - There are currently no logon servers available to service the logon request.

There may be many reasons for this special situation. In most cases, the order of domain services on the affected domain controller is incorrect.