Link to home
Start Free TrialLog in
Avatar of Stuart Saxby
Stuart SaxbyFlag for Australia

asked on

Cannot connect to AWS instance using RDP (remote desktop cannot connect to the remote computer)

I'm setting up an AWS instance to test run software on.  Unfortunately I'm not able to RDP to the machine.

I've set a public IP and opened up all ports.

Here is the instance settings:
User generated image
Here are the security settings.
User generated image(same for outbound)

Errors are here:
User generated imageUser generated image
Any assistance on how to troubleshoot further would be appreciated!
Avatar of George Khairallah
George Khairallah
Flag of United States of America image

Just throwing this out there ... Are you sure you deployed an AMI that has full windows server instead of server core, which doesn't have RDP access ?

I recently helped a friend who sent hours looking on the AWS settings and security groups and his problem was in the deployed AMI all along :)
Avatar of Stuart Saxby

ASKER

It's possible, how can I tell?  I launched an instance straight from the 'Quick Start' options after clicking 'Launch Instance'.
User generated image
SOLUTION
Avatar of Stuart Scott
Stuart Scott
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Feel free to post the obvious - I only know just enough to get myself in trouble.

Here's the internet gateway settings -
User generated image
Here's the ACL settings -
User generated image
I couldn't remove the 'deny' part, when I edit the rules it's not an option.  I tried creating a 0.0.0.0/0 access for ICMP Echo replies, and then one with my computer's public IP but no luck.

I'm not sure how to do this one -
then make sure you have a route from your public subnet which routes traffic to 0.0.0.0/0 using the IGW

Also, here's the VPC connected to the EC2 instance -
User generated image
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It didn't!  I've updated the route table so it has the two entries.
User generated image
Unfortunately still can't ping...
User generated image
Apologies in advance if the solution is something dumb I've done.  Any ideas for next troubleshooting?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I'd set up an 'elastic IP' so I changed the subnet to generate an IP and created a new instance.  Unfortunately didn't help.

Here's the log and screenshot.
User generated imageUser generated image
Current settings.
User generated imageUser generated image
Gateway and routing
User generated imageUser generated imageUser generated imageUser generated imageice_screenshot_20170530-144824.png
Also tried pinging on my mobile data rather than local network to see if it's something there.  No response either.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for all the help!  After getting all the security and network settings correctly, turns out you can't ping the Windows Server 2016 instance.