1 Answer
- Newest
- Most votes
- Most comments
1
Find the EC2 instance in AWS Console, and check it is running.
Confirm that its public IP address is still the one that you are trying to connect to (if the instance was stopped for a while and then restarted its public IP will have changed).
Check that the security group(s) applied to the instance allow inbound connections on port 3389/tcp (for RDP) and that inbound ICMP is enabled (for ping).
If all of the above checks out then the next thing to check would be connectivity and routing for the subnet in which the EC2 instance is running.
Relevant content
- asked 3 years ago
- asked 4 years ago
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
I have rebooted, the public IP is the same, 3389/tcp is enabled. Subnet and routing looks right. We have not changed anything since the last time we accessed this server.
Inbound 3389/tcp from anywhere (0.0.0.0/0)? If it isn't then try expanding the security group rule to be that.
(I assume in all this that you are trying to get access over the internet, and not over Direct Connect or VPN).
Also, are you able to view the EC2 system console screen, just to check that the instance is up and running properly and displaying the Windows login screen?