- Newest
- Most votes
- Most comments
Ive already terminated the instance and launched a new one.
The public IP address of the EC2 instance will be different for your new instance, ensure you're connecting to the correct IP address.
The password will be different too (although I know that you're not even able to establish the initial connection right now).
Has the IP address of the local device changed? If it has then the security group may need to be updated to reflect this? It may be worth opening 3389/tcp from 0.0.0.0/0 while troubleshooting, you can always tighten this up later.
In the AWS Console is the Status check of the instance showing 2/2 checks passed ?
Depeding on the region, you may be able to select the instance and selecting Actions -> Monitor & troubleshoot -> Get instance screenshot. This should show you the system console, does this look like the system is running?
Hello.
If your EC2 instance is registered as a managed instance in Systems Manager, you may be able to troubleshoot it by following the steps in the document below.
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/troubleshoot-connect-windows-instance.html#rdp-issues
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/troubleshoot-connect-windows-instance.html#Troubleshooting-Remote-Desktop-Connection-issues-using-AWS-Systems-Manager
Im not certain its an issue listed in one of these. I deleted the old t2 instance with its corresponding ebs and created a new one with the existing key pair and security. The issue is the same - error connecting to rdp.
Is a route to the Internet gateway set in the route table of the subnet where EC2 is running? Also, is RDP allowed in the inbound rules of the security group in EC2? Please also check that all communication is permitted in the network ACL of the subnet where EC2 is running.
As far as I can see, RDP is allowed in the inbound rules under security tab. Where do I find the route to the internet gateway? Instance id: i-08333163856d5f233
You can check the subnet ID where EC2 is running from the EC2 networking tab.
Click on the subnet ID to check the details of the subnet. If the route to the Internet gateway is set, the settings should look like the image below.Is it possible region Im connected to is experiencing some kind of downtime?
I don't think there are any failure reports from AWS so far. By the way, are the username and password used for RDP connection correct? If you recreated EC2, the Administrator password should have changed, so you need to confirm it again using the key pair.
Yes the route has been set in that case, and I still cannot connect. Is it possible region Im connected to is experiencing some kind of downtime? Ive already terminated the instance and launched a new one. So I dont know what else I can do.
Relevant content
- asked 10 months ago
- asked 2 years ago
- asked 8 months ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 years ago
I launched a new instance and the problem was still there. So I deleted everything including the security group and key pair and started afresh. Its working now. The only thing was I had to redo the custom settings on the ebs and reinstall the applications.
Come to think of it, its possible there was something to do with the security group because only after I deleted it, and created a new instance did it finally work. But my ip had not changed. I have been on a static ip for 5 years.