Hello,

I recently upgraded to Windows 8.1 and I am trying to access my work PC from home which goes through VPN.  I see my PC trying to connect to my work PC.  When I do mstsc /span I am getting a remote desktop internal error occurred.  This did not happen until I upgraded to 8.1.  It worked well on Windows 8.  How do I get the Remote Desktop Connection to work now?

Hi,

First, I consider that this issue can be caused by incompatible drivers, please update your network adapter driver and video card drivers to check the issue first.

Also, please try to reset RDP for testing:

How to Reset and Clear Remote Desktop Connection History in Windows 7 and Windows 8
http://www.eightforums.com/tutorials/25423-remote-desktop-connection-clear-history-windows.html

Then, please let me know what you use to connect VPN:

1. Create VPN connect in control panel

2. VPN client

3. DirectAccess

In the following, please let me know if you can ping the remote computer.

If not, please check whethether the RDP port is allowed in Firewall.

To further help you, please upload the event log here for research.

Im having the same issue, I updated to 8.1 a few months ago. Everything was working fine up until this morning. No I cannot RDP any servers.

I have setup my router to create a persistent pptp tunnel to my firewall at work. I can ping all my servers from my home network. When I try RDP 2003/2008 servers I get a message stating An Internal Error has Occurred. When I try one of my 2012 boxes it throws an error stating some licensing issue. 

Im having the same issue, I updated to 8.1 a few months ago. Everything was working fine up until this morning. No I cannot RDP any servers.

I have setup my router to create a persistent pptp tunnel to my firewall at work. I can ping all my servers from my home network. When I try RDP 2003/2008 servers I get a message stating An Internal Error has Occurred. When I try one of my 2012 boxes it throws an error stating some licensing issue. 

I just got this problem now (held off on that update until today (3/14/2014)).  Now I can't use my Windows 8.1 machine to connect to a server using RDC.

Im having the same issue, I updated to 8.1 a few months ago. Everything was working fine up until this morning. No I cannot RDP any servers.

I have setup my router to create a persistent pptp tunnel to my firewall at work. I can ping all my servers from my home network. When I try RDP 2003/2008 servers I get a message stating An Internal Error has Occurred. When I try one of my 2012 boxes it throws an error stating some licensing issue. 

I just got this problem now (held off on that update until today (3/14/2014)).  Now I can't use my Windows 8.1 machine to connect to a server using RDC.

I have the same issue. I can ping the remote pc, but when I try to connect using Remote Desktop, Windows 8 returns "An internal error has occurred."

*ping* I have tried a number of solutions out there with no luck either.  

I had no issues in the past with Win 8 desktop->Win 7 mobile, Win 8 desktop->Win 8 mobile,  Win 8.1 desktop>Win 8 mobile, and even Win 8.1 w/update->Win 8.  Now with Win 8.1 w/update->Win 8.1 (no update) mobile I see my issue.  I have been trying to fix this, off and on, for the past month+.  Back on it now.

Would anyone else have any suggestions?  Thanks!

I have this issue on a Windows 8.1 box (fresh install from Windows 8.1 media -- not an upgrade from Windows 8.0).

Once I VPN, I can ping the PCs I am trying to connect to.

Further, I can telnet to the RDP port, too!!!

e.g.,

telnet ipaddy 3389

Trying ipaddy...

Connected to ipaddy.

Escape character is '^]'.





Old question but I hope it helps someone. A corrupted CAL license issued to your local client could be the issue. Try these steps on the local workstation (NOT THE SERVER):

Delete the registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

-OR-

Use this Microsoft Fix it for me.

http://support.microsoft.com/KB/187614

• Edited by Ninja Bem 16 hours 54 minutes ago

Old question but I hope it helps someone. A corrupted CAL license issued to your local client could be the issue. Try these steps on the local workstation (NOT THE SERVER):

Delete the registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

-OR-

Use this Microsoft Fix it for me.

http://support.microsoft.com/KB/187614

• Edited by Ninja Bem Thursday, February 05, 2015 6:50 PM