Connect with rdp to Amazon EC2

0
votes

Ok, I create an Instance in AWS and follow all the points in manuals, videos, etc. But I receive 'Cant connect to server because firewall, shutdown, etc'

I configured the following:

Instance:

  • Private IP OK
  • State: Running
  • Checks: All ok
  • Public DNS: OK
  • Public ip: Ok
  • Elastic IP Attached: ok
  • Network interface attached (And this network has security group, ips, etc)
  • Security Group (Not default):

INBOUND

Type Protocol Port Range Source

RDP TCP 3389 0.0.0.0/0

SSH TCP 22 0.0.0.0/0

HTTP TCP 80 0.0.0.0/0

HTTPS TCP 443 0.0.0.0/0

OUTBOUND

All traffic All All 0.0.0.0/0

Default (Not in use) has the same options, but he puts at the final one 'DENY ALL' for all ports. I changed to the other security group in order to try when I create a instance and Amazon ask me if attach new security group with my rules.

Well, I create an AWS EC2 instance, I read all the options, configure all, and I push in connect, download the RDP, get the password, and execute it and never connect.

I has too a VPC, with route table:

Destination Target Status Propagated

172.31.0.0/16 local Active No

0.0.0.0/0 igw-7b887612 Active No

Internet gateway igw-7b887612 atached to default vpc vpc-a611ddcf, subnets with route table and networks acl with inbound/outbound RDP TCP from 0.0.0.0/0

I see public ip, dns, security rules, etc all ok. I try to connect from a Windows 8, and i can connect to others remote desktops, but not created in amazon :(

I don't know what more see for connect to the server :/ Any idea?

EDIT: IMAGES OF ALL, instances, ips, security groups, etc

http://imgur.com/miTd4YF,qLug0bV,ZevVI3j,jH86IpZ,pDYB8b0,p8Mj728,X5TCYqZ,EF2s4yy,hafFmIP

1
amazon-web-servicesamazon-ec2rdp
It looks like you used the wizards to create your VPC, so the networking all looks correct. Can you ping the IP address? – Mike
Also, a critical point...... Make sure you change the elastic IP once your problem is solved! It is a massive security risk to show to the world your public facing IP addresses, as well as what open ports you have. The best thing would be to disassociate and release that elastic IP and get a new one, that you keep private! – Mike
I ping the IP Aand not answer, and yes i know i need change ip when all work but im crying because i cant never connect to this machines :/ – Worvast
Have you made sure your inbound rules match your outbound rules on your security group and your NACL? If you can't even ping it, then it sounds like there might be some problem with your networking. Can you successfully RDP to any other non-AWS machine? – Mike

1 Answers

-1
votes

please check and ensure you have enable your remote access for your machine in Windows, and please ensure also you are doing a remote using the administrator / remote access allowed accounts.