I'd check the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have a server that is experiencing strange issues.
We loose the ability to RDP into it a day or two after it's rebooted. It cannot access the \domain\sysvol share and when we can't RDP into it any use of remote powershell to it results in a hung powershell session.
CPU usage is minimal. Printer and Files shares continue to function correctly. We just can't seem to login to the server using RDP at all.
Some times we can attach the Services.msc to it remotely. When we can do that it takes forever for any refresh to take place. I restarted a single service this way and it took almost 5 minutes to get control back again in the services.msc.
There isn't anything in the Even Logs that is jumping out as to what the problem is.
Have you seen anything like this before, how did you troubleshoot it?
I'd check the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Nope, that's not it. DNS is clean and there are no IP conflicts and both have static IP's with static DNS entries for them.
We loose the ability to RDP into it a day or two after it's rebooted. It cannot access the \domain\sysvol share
Sounds like a firewall profile change was likely. When NLA starts to detect the network location, the machine will contact a domain controller via port 389. If this detection is successful, it will get the domain firewall profile (allowing for correct ports) and we cannot change the network location profile.
If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Hi there,
Try using the shutdown command from another server to do the reboot and see if it behaves normal after the reboot.
Does the server have multiple NICs? You might face these issues when terminal services service binds to the wrong one. Also if you have made any recent updates try uninstalling them and see if that is helpful.
The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.
Remote Desktop Connection Broker not starting after reboot
------------------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer--