These instructions are great for Windows to Windows, but could someone suggest asimple alternative for a Linux (remote, behind the firewall) to Windows (server). Also, can the tunnel on the server end be set to passively listen for incoming connections?
Paul On Friday 14 December 2007 4:57:07 pm Scott C. Best wrote: > Thomas: > > Hello! You're unable to connect from work to home because > (most likely) your workplace firewall is blocking outgoing connections > to the TCP port that your VNC Server at home is listening to. That is, > by default, a VNC Server listens to TCP 5900. If you changed that to > TCP 443, and tried to connect from work (eg, 100.200.300.400::443), > you may have more success. Many workplace firewalls block connections > to anyting but a handful of "common" applications, like HTP, HTTP, > and HTTPS. The last one, HTTPS, uses TCP 443, and it's the best one > to "borrow" when you need to. > > If that doesn't work, you may have to "tunnel" the connection. > Here is an example of using EchoVNC to tunnel a RealVNC connection from > home to work (which is usually harder): > > 1. Download EchoVNC 2.31 and install it on the PC you want to > take remote control of (eg, your work PC). The startup Wizard > will automatically detect your RealVNC server and configure > itself to work with it correctly. > > 2. During the Startup Wizard process, login to the demo echoServer > at "demo.echovnc.com", password "demo2007". If your workplace > firewall doesn't allow that, try "demo.echovnc.com:443", same > password. The login name you use in this step is how you'll > connect to this PC in the future. > > 3. Download EchoVNC 2.31 and install it on the PC you want to > take remote control from (eg, your home PC). During the Startup > Wizard process, login to the same echoServer you chose in step > #2 above. > > 4. Start the Viewer. In the Options screen, tell EchoVNC to use > the RealVNC Viewer installed on your PC. > > Once those steps are done...in the main GUI of the Viewer, > use the little "search box" to type in the login name of your VNC > Server, the one you connected with in step #2. Once you find it, > just double click. That should do it! > > cheers, > Scott > http://sourceforge.net/projects/echovnc > > > Hi all, > > > > I installed the Real VNC Server on my computer at home and the client > > viewer on the computer in my office (in the company). I open the viewer > > in my office trying to connect the server at home, but I got error: > > "unable to connect to host: Connection timed out (10060)". > > > > I call my friend in other city at home trying to connect to my > > computer at home, it runs. I am not sure it's because of the fire wall > > of my company. > > > > Besides, if I ping the ip-address of the computer at home. I get > > response. > > > > Someone knows how to overcome it? > > > > Regards > > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list