A
A
alovanton2015-07-16 21:50:57
Domain name market
alovanton, 2015-07-16 21:50:57

Problems with a domain controller during an emergency shutdown, how to solve?

After restarting the server, there were problems.
All the logs started to be red, up to this point everything was, as it were, smoothly.
42a489b7820e49e0a2e22784e178c50d.JPG8cb6b0b2e49b4c3bae9b2f991661814d.JPG
I can't access the terminal servers with an error:
"The specified domain does not exist or it is impossible to connect to it."
Need help! I would be grateful for any help!
Thank you.
PS:DNS server failed to open Active Directory. This DNS server is configured to receive and use directory information for the specified zone, and without it, it cannot load the zone. Check if Active Directory is working properly and reload the zone. The event data is the error code.
It's strange that I didn't add a new controller...
PS2: An error occurred while processing group policy. Failed to resolve computer name. Possible causes:
a) Name resolution error on the current domain controller.
b) Active Directory replication lag (an account created on another domain controller has not yet replicated to the current domain controller).
It's strange, somehow that's all ... I didn't make any changes in the controller.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
A
Andrey Ermachenok, 2015-07-16
@eapeap

There was something similar Why is the server unavailable via RDP after a reboot?
I think you need to restart the terminal server with DC enabled

V
Vitaly Pukhov, 2015-07-17
@Neuroware

The first solution in any situation, if you absolutely do not know how to fix something - reboot. 99% of existing problems are treated with a reboot. If it does not help, you will continue to shaman.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question