4

Remote Desktop to EC2 Instance on Port 80 or 443

view full story
linux-howto

http://serverfault.com – I created a small EC2 instance running Windows Server, and opened up ports 80, 443, and 3389. I needed to Remote Desktop into it from work where the outbound firewall only allows 80 and 443. So I modified the registry entry as outlined in this document to have Terminal Server listen on port 443. However when I tested it by pointing Remote Desktop to the address and port ( ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com:443 ) it wouldn't connect. I was testing this from home, not from work, where a standard connection was working fine before I changed it. Why not? Could it be that Amazon doesn't (HowTos)

u85500's picture
Submitted by u85500 on 06/06/2012 – Made popular on 06/06/2012

Stories similar to Remote Desktop to EC2 Instance on Port 80 or 443

Here is what I am trying:

Launch ami-c98d55a0 with t1.micro size and a security group with inbound tcp ports 139, 445, 3389 open.

I have a web server, which was working fine. It also was an FTP server and a Windows Remote Desktop server, all working fine. Someone called our ISP to increase the internet speed, and suddenly nothing works - I can connect with Teamviewer, but HTTP, FTP & RD doesn't work.

Problems with remote desktop 3 years 17 weeks ago

I am not sure where the problems lies, but I have been trying to use remote desktop (using KRDC) to work on my friends computer with Ubuntu 9.10 on it. I have everything set up right, but it is horribly inconsistent. I have set up port forwarding on her router, but though that helped at one time, it doesn't anymore.

I have a trouble with RDP on Windows server 2003. When I start the system everything seems to work (3389 port is listening), I can connect with rdp client, just after login confirm the client exits and then the Remote Desktop stops (3389 is not listen anymore).

I have a server (Win 2008) and a desktop PC (Win 7) at my work behind a firewall.

Connection to Remote server 27 weeks 15 hours ago

I am using squid 2.7 as a forward proxy.

I need to establish a remote connection to the internet server 188.x.x.x on port 3306 from my local IP 10.1.1.1.

I have a t1.micro instance with public dns looks similar to

ec2-184-72-67-202.compute-1.amazonaws.com (some numbers changed)

On this machine, I am running a django app

$ sudo python manage.py runserver --settings=vlists.settings.dev Validating models...

0 errors found Django version 1.4.1, using settings 'vlists.settings.dev' Development server is running at http://127.0.0.1:8000/

I have ope

I'm trying to connect to my remote mssql server for my GunZ private server, but for some reason i get the following error

Cannot connect to 94.xx.xx.xx.

ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process.

Hi all,

So I have an issue, in which I setup a reverse ssh connection on a virtual backtrack instance, which connects to a relay server of mine.