The nuclear option, avoid if you can, save for last resort. RDS is broken, had to reinstall RDS completely. All services were running on the PDC, rebooted the PDC, once it came back up it was fine. The primary domain controller stopped servicing requests, so 50/50 chance you would get the internal error, and it sticks for that user session. It was hit and miss, with two DNS servers running on domain controllers under the NIC, users logging in queried a random DNS server. Server Manager > Tools > Terminal Services > Remote Desktop Licensing Manager > Server was not activated, or not added into the right AD security group (click yellow triangle if present). One of the Remote Desktop Services was not running. , rather than RDS.local or something internal. If you use RemoteApp, ensure the DNS address is what people use to connect to, e.g. If you don't have a publicly signed SSL, it's time to get one. PFX (private + public keys) to a browse-able file to be imported via the Server Manager. Namecheap has $10 SSLs, Use IIS > Server Certificates to generate (2048 bit Microsoft RSA) and complete your request with the SSL provider's signed. Solution was to reimport the publicly signed SSL with private key on the server (.PFX).
On Server > Server Manager > Remote Desktop Services > Deployment Overview > Properties > Certificates, despite being present for a year, suddenly the SSL was not defined. Don't know why a RDP client would need them, but it worked.
Solution was changing properties on those services and enabling and starting them. The SSDP Discovery and UPnP services were disabled or stopped on the RDS. "An internal error occurred" is a generic catch-all error that can happen for any number of reasons. I've seen this 20+ times in the last two months across 20 different RDS servers in completely separate domains. The relevant status code was Object already exits.Īnyone come across this since 1903? I have done some searching and nothing overly helpful has come up. The RD Session Host Server has failed to create a new self signed certificate to be used for RD Session Host Server authentication on SSL connections. I thought the error could be pointing to the NLA so disabled that, no difference. Removed my laptop from the Domain - added it back on again- nope Error message An internal error has occurred pops up and that's it.Ĭhecked the RSA - Machine Keys, in fact deleted the keys I could and let them re create. I have three users who have upgraded to 1903 (myself included, I did mine as a test the others did theirs as they felt like it)Since the upgrade been unable to RDP to anything. Been lurking here a little while, first post.
0 kommentar(er)
