Hey everyone! Welcome to my blog. Today, I’ll be sharing my experience with a recent issue I faced where the Remote Desktop Protocol (RDP) showed an “internal error has occurred.” Interestingly, I came across a blog post yesterday by Brandon Lee on virtualizationhowto.com that addressed the same problem. So, I thought I’d share my story and how I resolved it. Let’s dive right in!
Last Friday, when I tried to access a server using RDP, I was greeted with the error message “internal error has occurred.” I suspected it could be one of the issues mentioned in Brandon’s blog, but I needed to log in to the server to troubleshoot further.
Failed Login Attempts:
To my surprise, I couldn’t log in to the server from the console either. It kept denying my login, saying my password was incorrect. I knew that wasn’t true because I had used it before without any issues. So, I tried the local admin password, but still no luck.
Using Hiren’s Boot CD:
I was running out of options, so I decided to use Hiren’s Boot CD to clear the local admin password. I left the password field empty, and that’s when I finally managed to log in to the server.
Discovering the Culprit:
Once inside, I discovered that the Carbon Black (formerly Bit9) security software was blocking all Windows services, including RDP. This was the cause of my “internal error has occurred” message and why I couldn’t log in with my usual credentials.
After identifying the issue, I went ahead and made the necessary adjustments to the Carbon Black settings to allow the Windows services, including RDP, to function correctly. Once I made these changes, I was able to use RDP without any issues.
So there you have it, folks. That’s how I resolved the “internal error has occurred” message in RDP. If you’re experiencing the same problem, make sure to check your security software, like Carbon Black, to ensure it’s not blocking essential services. And if you haven’t already, do check out Brandon Lee’s blog post on virtualizationhowto.com for more insights.
Thank you for reading, and don’t forget to share this post with anyone who might be facing similar issues. Stay connected for more tech troubleshooting stories and insights!
Here is a link to the video:
🔥Subscribe to the channel: https://bit.ly/3vY16CT🔥
🚨Read my blog: https://angrysysops.com/
👊My Podcast: https://bit.ly/39fFnxm
🔥vExpert info: https://bit.ly/3vXGPOa
🛒 VMware EMEA store: https://imp.i263671.net/c/3505578/814646/11461
🛒 VMware US store: https://imp.i263671.net/c/3505578/814642/11461
🛒 VMware APAC store: https://imp.i263671.net/c/3505578/814645/11461