HTTPort & HTTHost

Piccolo · Post by **Piccolo** » 2005-12-31 07:47

HTTPort allows you to bypass your HTTP proxy, which is blocking you from the Internet. With HTTPort you may use various Internet software from behind the proxy, ex. e-mail, instant messengers, P2P file sharing, ICQ, News, FTP, IRC, etc.

The basic idea is that you set up your Internet software in such a manner, that it connects to your own local PC as if it was the remote server it needed. HTTPort then intercepts that connection and runs it through a tunnel through the proxy.

HTTPort doesn't really care for the proxy as such, it works perfectly with firewalls, transparent accelerators, NATs and basically anything that lets HTTP protocol through. HTTP is the basis for web surfing, so if you can freely surf the web from where you are, HTTPort will bring you the rest of the Internet applications.

HTTPort performs tunneling using one of two modes. The following schemes will give you the idea.

redge · Post by **redge** » 2005-12-31 14:34

step by step how to configure httport with UltraVNC ?
what need on vnc server ?
what need on vnc viewer ?
Where to install httport on which side ?
thank you a lot.

badillo · Post by **badillo** » 2006-01-04 21:47

redge wrote:step by step how to configure httport with UltraVNC ?
what need on vnc server ?
what need on vnc viewer ?
Where to install httport on which side ?
thank you a lot.

EXACTLY!!! i could use this program, but i dont have any idea on how to use it, and every manual out there is too complicated (at least for me)... any help anyone?

Piccolo · Post by **Piccolo** » 2006-01-05 07:32

httport&htthost is just a turnneling through software.When a Wan VNCView_ssl can not connect WinVNC in Lan Because Strong Firewall and proxy.Maybe httport&htthost is OK.

rmoller · Post by **rmoller** » 2006-01-05 16:23

I used htthost/httport long ago for VNC forwarding.

You need to install htthost on a PC, who is generally accessible on the internet - typically your "home" PC. This means that if you started a webserver on the home PC, everyone else must be able to connect to it. There are two showstoppers for htthost on home PCs:

NAT/firewall issues: You need to enable an incoming port. For HTThost it will typically be 80(http) or 443(https), but any port can be used - IF the HTTP proxy at work supports it - some proxys are configured to allow only 80 and 443.

DNS issues: If your home IP address is dynamic, you need to use a DynDNS service to be able to address your home PC as f.ex. https://myhome.dyndns.com.

You need to install httport on the machine on a LAN protected by a HTTP proxy - typically a "work" PC. HTTPort needs to be configured with the same HTTP proxy address as your browser. It also needs to know the URL to get to your "home" PC - f.ex.

http://myhome.dyndns.com or https://12.34.56.78

HTTPort must be configured to listen on a port, say 5999 and forward to remote port 5900, if you want to control home pc from work. The VNCviewer on work PC should connect to , say 127.0.0.1:99 . HTTPort accepts the connection, goes through the proxy to HTTHost on your "home" PC. HTThost will forward connection to winvnc on port 127.0.0.1:5900 on your "home" PC.

Work PC VNCviewer.exe
|
V
TCP port 59xx
Work PC httport.exe
|
V
HTTP proxy on work
|
V
TCP port 80,443 or other if proxy accepts
Home NAT router with incoming port forwarding enabled
& with fixed IP address or dyndns assigned
|
V
TCP port 80,443 or any other
Home PC htthost.exe
|
V
TCP port 5900
Home PC winvnc VNC server

Remember to configure winvnc on the "home" PC to allow loopback connections, because htthost will also be running on your "home" PC.

You need someone's help if you are not familiar with TCP/IP and HTTP(s).

Reverse connections can be made in similar way, but can only be initiated from "work" PC inside the proxy.