2022 Server randomly requires reboot due to "The RPC server is unavailable." error

Question

I have a 2022 Server that randomly (usually once daily, no specific time) stops allowing RDP and local logins. It throws an RPC server is unavailable error. Any one still logged in remains in, though they are unable to reset/shut down the server. When attempting to do so via cmd prompt it returns RPC error as well. Any new login get the error after typing in user/PW. Doesn't matter if it's a domain or local account. Only way to get past this is a hard reboot.

After the reboot things return to normal and logins happen just fine. This is a VM running in Nutanix AHV. Things I've tried so far:

Upgrade VirtIO driver

Checked DNS

Checked Time

RPC service is running
Remote Registry isn't running, but it is set to auto start (triggered). Checked other working servers and it was set to this.

Checked this page from MS

https://learn.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/not-log-on-error-rpc-server-unavailable

UPDATE:

To save everyone some reading, there appear a common factor between a lot of the community. Sentinel1. Some users are reporting uninstalling it has fixed there issue. Others are downgrading versions.

Answer 1

We are in the exact same boat, and it doesn't affect all instances of Windows Server 2022 we operate. This is also NOT a domain controller. DNA, System Time and Zone, etc. as you highlighted do not work out.

Answer 2

Additional Detail:

Windows Server 2022 VM Running on ESXi 8

IIS Server Role

21H2 (20348.2582)

One observation I can make on this machine, this instance was the only one we did an in-place upgrade for (Server 2016 -> Server 2022). Not sure if it is relevant but, coincidentally, also the only one experiencing this.

Answer 3

Hello,

There are some details you need to pay attention to:

1. Verify correct DNS settings on both machines. Make sure that they can resolve each other's hostnames and IP addresses correctly. You can use the commands nslookup <hostname> and ping <hostname> to test DNS resolution.
2. Verify that the following services are running and set to auto start after restart on both machines:

• Remote Procedure Call (RPC)
• Remote Procedure Call (RPC) Locator
• TCP/IP NetBIOS Helper
• Remote Registry
• Windows Management Instrumentation"

3. Check firewall configurations to ensure that RPC-related ports are not blocked. You can temporarily turn off or disable the firewall as well as any third-party security software on your device as a test.
4. Update the network adapter driver.

If the problem persists, look for RPC-related error messages in the application log and system log in the event viewer.

References:

How to configure RPC to use certain ports and how to help secure those ports by using IPsec - Microsoft Support

How to Fix “The RPC Server Is Unavailable” Error in Windows 10? — Auslogics Blog | Tips to Diagnose & Resolve Computer Issues (Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information).

I hope this helps. If you have any follow-up questions, please contact us.

Best regards

Jacen

Answer 4

I've tried all the things listed above. Local logins do not work as well, so it shouldn't be anything network related.

I've got a ticket open w/ MS. I'll update when I get a solution.