Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Cannot RDC into my instance

0

Hello, i've been trying to connect to my EC2 instance for two days now, it worked 3 days ago. The issue was that the RDC limit was 2 ( i know it's the default), however i have a License Manager server configured and it's user based. I've been talking to Amazon Q and did some things it suggested and now i'm locked out of my instance. The error i get now is: We couldn't connect to the remote PC because no license servers were available to provide a license. Contact your network administrator for assistance.

Error code: 0x101

Topics
Management & GovernanceCompute
Tags
Amazon EC2AWS License Manager
Language
English
asked a month ago27 views
1 Answer
0

I understand you're experiencing RDP connection issues with your EC2 Windows instance. Based on the error you're receiving about license servers not being available, this appears to be related to Remote Desktop licensing configuration rather than the typical connection issues.

To help troubleshoot your RDP connectivity, I recommend using the AWSSupport-TroubleshootRDP automation document through AWS Systems Manager. This tool can help you:

  • Verify that Network Level Authentication is properly configured
  • Ensure the Remote Desktop Service (TermService) Startup Type is set to Automatic and the service is running
  • Confirm you're connecting to the correct RDP port (default is 3389)
  • Verify that Remote Desktop connections are allowed on your instance
  • Check the Windows Firewall settings
  • Restore default RDP configurations if needed

The licensing error you're encountering suggests that your instance may be configured to require a Remote Desktop Licensing server, but it cannot locate one. This could have happened if changes were made to the RDP licensing mode or configuration during your troubleshooting attempts.

If your instance is managed by AWS Systems Manager, you can run the AWSSupport-TroubleshootRDP automation to help restore proper RDP functionality. If the instance becomes completely unreachable, the AWSSupport-ExecuteEC2Rescue automation document is available, though note this requires stopping and restarting the instance, which will result in data loss from instance store volumes and a change in the public IP address.

I recommend starting with the AWSSupport-TroubleshootRDP automation to attempt to restore your RDP access without requiring an instance restart.
Sources
Troubleshoot issues connecting to your Amazon EC2 Windows instance - Amazon Elastic Compute Cloud

answered a month ago
EXPERT
reviewed a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content