[EMAIL PROTECTED] wrote:
>
>
> Is there a quick and dirty method of getting the viewer to access my home
> computer from here at work behind the firewall? Any help would be
> appreciated as this has become a vendetta of mine. I am determined to get
> this working. :-)
>
So how about your firewall? What do you know about it? Here's one way of
learning more about it.
Suppose you have a telnet client at hand:
If "telnet yourhost 590x" gives you "rfb 003.003" you know you can talk
to your vncserver from behind the firewall.
If "telnet yourhost 580x", and typing "GET / HTTP/1.0" gives you HTTP
response headers and html-source, you know you can talk to your
vncservers httpd.
Suppose both of these tests pass, but you still can't use the common
java vncviewer. In that case your telnet client is probably configured
to use a proxy, like Socks, or maybe a special telnet gateway. Good: you
can use a tunnel through that.
Suppose both of these tests fail. Test if you can connect out on other
ports by telnetting to other servers. If you don't have a httpd running
at home, just try "telnet www.yahoo.com 80" and do a HTTP request
manually. If this fails, and using your browser to surf to yahoo works,
then you know you will need a tunnel through whatever proxy your browser
is configured to use, probably http, maybe socks.
Let's say you're dealing with a http proxy. Again use telnet, the
proxy port is probably 8080, maybe 80, 3128, 8000 or yet something else.
Try telnetting to your vncserver with something like this:
telnet your.proxy 8080 , GET http://your.vnchost:580x HTTP/1.0
You should get HTTP response headers and html-source.
Then try:
telnet your.proxy 8080 , GET http://your.vnchost:590x HTTP/1.0
You will get an error from the proxy, but your vnc log will show if you
were able to connect this way.
Another way to test your connection would be trying the http tunneling
Java telnet applet you can find in my sig. It supports 3 different
connection
methods:
*normal/direct.
*plain forwarding (simular in effect like the patch you already tried,
for use with packet filtering firewalls).
*proxy tunneling (http or socks).
You can use it to telnet to your vncservers http and rfb port.
While this would seem to provide for the quick method you're looking
for, it's just too dirty to use it with VNC:-(
BTW. I just tried HTTPS tunneling today. It works, but
java.net.HttpsURLConnection won't use a persistent connection to the
proxy, resulting in multiple HTTP-CONNECT requests, and multiple=too
many with VNC. Hoping I can fix this, but my guess is not.
Anyway: once you know what you're dealing with, it's easier to find a
solution.
--
Harmen
http://www1.tip.nl/~t515027/brandgang/
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
