Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

VNC Single Click through AWS firewall

Post Reply
Timon912
Posts: 2
Joined: 2014-04-30 23:12

VNC Single Click through AWS firewall

Post by Timon912 »

Hey, guys and gals. I have an issue that I'm stuck on. My networking skills are at the novice level so I would appreciate any help. I have an AWS server, a free mini server, running Windows 2012 on their cloud. I want to control that virtual server with my home PC using VNC Single-Click (ChunkVNC). The problem is that I can't seem to connect directly from the server to my home PC. I'll explain below.

Here's what I CAN do
- connect from my home PC to AWS using Windows RDP.
- connect from my home PC to AWS using TeamViewer and GoToAssist (Citrix).

Therefore, I know that I can connect SOMEHOW to the server and remote control it. I know that TeamViewer and GoToAssist use a server out on the net that both parties connect to...but I'm not sure how Amazon does their RDP. I do know that they tell you to use 54.186.235.77, their DNS server for those virtual PCs, to connect with RDP.

Here's what I CAN'T do
- Ping my PC from the AWS server
- Telnet using port 3389 to my PC from the AWS server

Can somebody help me figure out what hardware would I need to buy to do this with VNC single click: dedicated server running repeater, etc?

I'm happy to move this conversation to the correct forum and perform any tests needed to answer these question. Thanks in advance.
Bonji
100
100
Posts: 339
Joined: 2008-05-13 14:54

Re: VNC Single Click through AWS firewall

Post by Bonji »

The issue isn't with AWS but with your home setup. You have to "publish" devices from your home network so they are accessible from the internet. Software that utilize repeaters get around this issue by allowing both end points to use outbound connections which typically are not blocked by a firewall.

You need to look into how to setup port translation on your home firewall. Here's a quick example:

homePC (192.168.1.11)
homeFW (192.168.1.1) (20.20.20.20)
remoteAWS (30.30.30.30)

Configure your home router to forward port 3389 to the internal IP of 192.168.1.11. You would then connect to that from the AWS server by telnet'ing to your home's public IP 20.20.20.20 on port 3389. Your home firewall then forwards the traffic from the public interface to the private IP of 192.168.1.11.
-Ben
Timon912
Posts: 2
Joined: 2014-04-30 23:12

Re: VNC Single Click through AWS firewall

Post by Timon912 »

Thanks very much for the response. You were pretty much right: 1) I had ICMP responses turned off on the router AND 2) I had my repeater PC only getting 5901 forwarded to it and not 443 (although, that should be open, no?). Putting the repeater PC in a DMZ ended up working as far as getting the AWS server to connect to the repeater using port 5500. Just like Borat, I very excite! Although, now there's an issue with connecting BOTH the viewer and the server to the repeater at the same time. I guess that I'll browse the forums for a bit and see what I can come up with.
Post Reply