text: RDP Internal Error - Microsoft Remote Desktop Services - Spiceworks
  RDP Internal Error
  by TheCraigster
  on Apr 10, 2019 at 19:27 UTC 1st Post
  I have a client running windows server 2012 and the clients are windows 10. their network is a comcast business router, and a cisco RV325 router. the public IP address has a mapping to the internal address for the server. When the user launches a remote desktop session, the remote directly into the server. I know this isn't ideal, but they are a very small shop, and this accomplishes their goal of being able to get into the network to run a custom application. Anyway, we set everything up, and we tested each of the laptops RDP'ing into the network and everything was working fine. After a few days of use, all of the sudden, all of the laptops that were working just fine started receiving an "Internal Error" whenever they tried to RDP into the server. I brought the suspect laptops home to troubleshoot the issue, and the laptops can RDP into the network from my home network just fine - I do not receive the "internal error" on these laptops when I RDP from my home network. Does anyone have any ideas what could be causing the internal error on their network? Any help you can provide would be very appreciative. Thank you!
  Rod-IT Apr 10, 2019 at 19:34 UTC
  spicehead-zxpr9 wrote:
  When the user launches a remote desktop session, the remote directly into the server. I know this isn't ideal, but they are a very small shop, and this accomplishes their goal of being able to get into the network
  It's not good practise, invest in VPN and use that. While you state they are a small shop if the wrong person gets in (and there are many ways outside of password cracking), they may no longer have a business.
  Do it right (VPN), protect their business.
  Rod-IT Apr 10, 2019 at 19:36 UTC
  You say all the laptops - how many?
  RDP access is only for administrators, if anyone else is using this you are also breaking the T&Cs. But ideally you want them to use VPN over RDP always.
  Unless and with some very fine tuning you restrict RDP to only their home IPs (which if dynamic change)
  TheCraigster wrote:
  the public IP address has a mapping to the internal address for the server. When the user launches a remote desktop session, the remote directly into the server. I know this isn't ideal
  This isn't just 'not ideal' it's extremely dangerous for your client. RDP open to the Internet means that they are almost certainly going to get attacked on a somewhat regular basis. Even if nobody gets in they can cause DoS issues with all the attacks.
  Apr 10, 2019 at 19:37 UTC
  I have a client running windows server 2012 and the clients are windows 10.
  Are the laptops trying to connect to the Server or to their Desktop machines? If the Server, you've got RDS setup and RDS CALs installed?
  TheCraigster Apr 10, 2019 at 19:52 UTC
  Thanks for the replies, but none of your replies address my question, which is related to the user receiving an "internal error" when they try to start up a remote desktop session from the laptop. We have addressed the security, we have the appropriate CAL's, we use a VPN server... and remote desktop worked just fine for about 3 weeks. now whenever the users try to connect they receive this error. But, I can take the same laptops to my home network and start a remote desktop session just fine. Can you try to address that with your replies, please?
  Rod-IT Apr 10, 2019 at 19:55 UTC
  https://community.spiceworks.com/topic/2085271-rdp-broken-internal-error-has-occurred?page=1#entry-7375527
  Rod-IT Apr 10, 2019 at 19:58 UTC
  You didnt share anything you've tried with us either.
  Rod-IT Apr 10, 2019 at 20:00 UTC
  Enable RDP connections only from secure NLA clients
  TheCraigster Apr 10, 2019 at 20:08 UTC
  You're correct - I didn't share what I already tried.. my apologies for that...
  I tried the suggestions in this YouTube video: https://www.youtube.com/watch?v=G5HoRI4kbIo
  I also went through the suggestions at this URL: https://appuals.com/fix-remote-desktop-connection-internal-error-has-occurred
  None of the items corrected the issue.
  Thank you very much for the link you provided - I will read through the post, and try the suggestion they talk about.. I believe that is on the right track, as the error started coming up after the users went through a windows update, and that may have updated something that caused the internal error issue. Thank you, again, and i'll update this post after trying it out.