This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
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.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
Has there been any update to this? We are noticing this on S1 customers as well. Sometimes we go for days without a customer calling in. Today we've had 3. Short of uninstalling S1, hard reboot (hold the power button) has been the only answer.
I've heard nothing. Yesterday we re-engaged with our S1 vendor to get this escalated. It is still ongoing for us as well.
Is everyone still having this issue? Where are you purchasing your S1 from? We use PAX8. Support has been subpar to this point.
We are for sure. Our S1 is provided to us by a reseller, so unfortunately I do not get to work with them directly.
We don't have concrete proof that this is a S1 issue yet. Our partner initially blamed DNS configurations and worked on the issue from that angle, HOWEVER, we now have more instances of windows being affected by this and it would appear DNS is not to blame. To my knowledge, all new issues are WS 2022.
The only machines that appear to have NOT been affected by this just yet are DCs themselves.
Jake
Same for us - I am shocked our DCs haven't crashed. If those crashed we'd be in a world of hurt. Currently its still my same ole list of server crashing. Almost none of them get past 15 days of uptime before it happens. All Server 2022 - we upgraded S1 from v23.4.2.216 to v23.4.4.223 SP1 but it doesn't appeared to have helped. There is zero chance my security team would flat out remove S1 or even disable it for any extended period of time here. Most I can do is pull a VM down and put it in my lab and see if it crashes after 15 days with S1 removed or find an alternative they'd agree with. We have no way to prove its S1 tho which is the biggest issue. I can ask my Security team to pull logs but they need an idea of what they are looking for in those. Gonna see what I can try here with valuable logs since I lost one this morning.