Using remote desktop to connect to a server, the RDP connection is using the server's public IP that's static.I'm able to connect to the remote server from other PC's with the same user account but this PC is getting the error: Remote Desktop Error: 'An internal error has occurred.' Computer is running Windows 7 x64The network is using a VPN back to the main location where the server is, and I'm able to ping devices on each network.One thing is that I can RDP to other severs outside of this network without issues, so to me it seems like an issue with the VPN even though it's online.Has anyone had this issue before? It was working fine a few days ago.Tried a system restore, restarted the network equipment etc..
A reddit dedicated to the profession of Computer System Administration.Community members shall conduct themselves with professionalism.Do not expressly advertise your product.More details on the may be found.For IT career related questions, please visitPlease check out our, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read!Checkout the Users are encouraged to contribute to and grow our Wiki.So you want to be a sysadmin?Official IRC Channel - #reddit-sysadmin onOfficial Discord -. Gents,We have a server farm consisting of: RDGateway, RDBroker, and 3 Application Hosts. We have noticed end users who have Remote Desktop Connection 8.1 are unable to connect through our RDWeb. They received the following error 'RemoteApp Disconnected: An internal error has occurred'We have found a temp fixed by removing a Windows Update that rolls back the mstsc client to 7.1 and starts working for users again.Problem is, this is a SaaS environment and it doesn't seem like the System Administrator wants to proceed with having to uninstall the KB from their side. Is there anything we can do on the farm to make it compatible?All Servers are 2K8R2 and have mstsc 8.1 as well. Any ideas?. This is going to be something your server admin has to resolve, sadly.The endpoints will benefit from 8.1's update to RDP.
You may be missing something on the endpoints though:Do your endpoints specifically have 2574819An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1In any event, there is some tracing you can do, since you are troubleshooting the RDWeb side. Netsh has some providers/scenarios you can use. Let me know if you want to try that.
To check, go to services- remote desktop services- right click- properties- log on tab- NETWORK SERVICE in present in the 'This Account' column 5. In this case, if you are using the AADServer Firewall (custom firewall used to secure Terminal Server, Application Server and Remote Desktop Connection) whitelist your IP Address in the. Create an RDP file (open mstsc and click Save after entering the servername) and in notepad add the line enablecredsspsupport:i:0 somewhere. This disables the expectation of security. When you then run the RDP file it should allow you to UNSECURELY connect and gain access to your server.