connecting from the office to my home

Scott C. Best sbest "at" best.com
Tue May 3 22:12:01 2005


John:

 	Heya. Sounds like you've got a really good workplace
firewall that's very smartly content-filtering. Have you tried
running your VNC Server on TCP-443? Since that port is commonly
used for encrypted HTTPS traffic, many content-filtering firewalls
simply ignore it -- traffic there is not supposed to be content
filter'able.

 	Also, when you try telnet'ing, do you see the RFB response?

 	Lastly, for tunneling software, the PuTTY SSH client requires
no installation, and can be configured to work with any http-proxy
your workplace is probably using:

http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe

 	Again, for this approach, you may need to run your SSH
server on TCP-443 for the same reasons as above. That's how I use
it here. :)

cheers,
Scott


> Setup:
>
> Home - WinXP Pro SP2 w/ RealVNC 4.1.6 Service via broadband router
> Office - WinXP Pro SP2 via large corporate LAN
>
>
> Test:
>
> Everything works fine connecting from a friends house.
> I can telnet my home from the office on the VNC port.
>
> Problem:
>
> Using Client - After entering the server name, and clicking [OK], I get "read:
> Connection reset by peer (10054)"
>
> Using Web - After entering the server name, and clicking [OK], I get
> "rdr.IOException: java.net.SocketException: Socket read Failed"