fpipe and VNC from a NAT'ed WinVNC server
Thu Jan 30 15:22:01 2003
I'm having a bit of trouble understanding what your final goal is.
Is this the scenario?:
You are behind a firewall at work.
You are allowed to connect to port 80 on arbitrary external IP addresses
You make that connection directly, without using a proxy
At home, you'd like to have something listen on port 80, and redirect
connections to port 5900 on that same machine.
Is that accurate?
If so, then here is what I would do:
Get bouncer ( http://www.r00t3d.org.uk/bin/bouncer-1.0.rc6-win32.zip )
Run bouncer on your home machine with this command line: bouncer --port
80 --destination 127.0.0.1:5900
This will caust bouncer to listen on port 80, and redirect connections to
port 5900 on the local machine
At work, run vncviewer.
Connect to your.home.ip.address:-5820
(this works, because vncviewer connects to 5900+(number after colon), thus
You do have to have the allowloopback registry setting, but it sounds like
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org]On
> Behalf Of Rick Mayweather
> Sent: Wednesday, January 29, 2003 3:12 PM
> To: email@example.com
> Subject: fpipe and VNC from a NAT'ed WinVNC server
> Hello VNC users.
> I've been trying to understand how to setup a reverse data pipe
> or reverse
> proxy, or whatever you call it between a NAT'ed VNC server and the office
> with a very restrictive firewall.
> I don't want to and can't install ssh, nor can I use the
> vncviewer -listen
> with the winvnc -connect ip.of.vnc.client trick.
> So I want to configure fpipe to setup a directed reverse
> connection from my
> home VNC server to the office. From a lot of searching the web
> and previous
> posts and reading the fpipe docs, i've not seen a clear example for doing
> this yet, nor is it in the faq, maybe it's just not clear in my head.
> Indeed, it would appear that fpipe is the tool, although i'm not entirely
> sure that it can actually do this?
> My understanding is that this registry key is crucial to be set,
> so that we
> can connect to ourselves due to the pipe, can someone confirm this?
> Type REG_DWORD set to 1
> Where 126.96.36.199 is the work IP address (just a demo IP) and the NAT'ed
> WinVNC home host is on a private network, 10.x.x.x.x or 192.168.254.x
> So this is how I thought it should be, but it does'nt work, what
> have I done
> WinVNC client
> c:\> fpipe -l 80 -r 5900 -i 188.8.131.52 184.108.40.206
> WinVNC server
> c:\> fpipe -r 80 220.127.116.11 -l 5900
> WinVNC client connects to it's own IP, aka 18.104.22.168 on port
> 5900 and is
> forwarded through the reverse datapipe to the remote host.
> c:\> vncviewer
> This does'nt work, but is about as close as I can figure out how
> it should
> Can we FAQ this?
> I have read this publication with interest.
Surf together with new Shared Browsing
VNC-List mailing list