Re: Office to Home -- unable to connect to host

2007-12-18 Thread Scott C. Best
Paul: Hello! Our EchoVNC Viewer port to Linux should be in beta by the end of this month. I'll be sure to send you a note once it's in a suitable state for trying out. cheers, Scott These instructions are great for Windows to Windows, but could someone suggest asimple alternative for a

Re: Office to Home -- unable to connect to host

2007-12-18 Thread Paul Kaplan
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

Re: ECHOVNC -Re: Office to Home -- unable to connect to host:

2007-12-15 Thread Scott C. Best
Thomas: Hello! Sorry for the confusion: "demo2007" is just the password to use to authenticate the EchoVNC connection to the demo echoServer. It's *not* the password you set in your VNC Server, to authenticate VNC Viewer connections. Two different passwords. :) cheers, Scott Hi steve,

Re: Office to Home -- unable to connect to host: Connection timed out (10060)

2007-12-15 Thread Seak, Teng-Fong
Please reply to the list. On Dec 14, 2007 7:05 PM, Dale Eshelman <[EMAIL PROTECTED]> wrote: > I use firefox browser addon which shows public IP of the server. There > used to be a web site checkip.com bout no more. A similar site is http://whatismyipaddress.com/ Time out means the IP

Re: Office to Home -- unable to connect to host: Connection timed out (10060)

2007-12-14 Thread Seak, Teng-Fong
On Dec 14, 2007 8:26 PM, Thomas Chang <[EMAIL PROTECTED]> wrote: > To your questons: > > I am sure of my own ip address. As I wrote in my email, I let my friend in > other city using VNC Viewer to connect the server in my home and it works. > > I guess the firewall of my company will block the con

Re: Office to Home -- unable to connect to host

2007-12-14 Thread Scott C. Best
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

RE: ECHOVNC -Re: Office to Home -- unable to connect to host: Connection timed out (10060)

2007-12-14 Thread Thomas Chang
Hi steve, thanks to the answer. But why should use the password "demo2007"? Can I use other one? ** Previously Scott Best said to John: John: Heya. Please try this: 1. Download EchoVNC 2.31 and install it on the PC you want to take remote control

Re: Office to Home -- unable to connect to host: Connection timed out (10060)

2007-12-14 Thread Thomas Chang
To your questons: I am sure of my own ip address. As I wrote in my email, I let my friend in other city using VNC Viewer to connect the server in my home and it works. I guess the firewall of my company will block the connection which goes out. One

Re: Office to Home -- unable to connect to host: Connection timed out (10060)

2007-12-14 Thread Seak, Teng-Fong
On Dec 14, 2007 8:02 AM, Thomas Chang <[EMAIL PROTECTED]> wrote: > 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: "una

Office to Home -- unable to connect to host: Connection timed out (10060)

2007-12-13 Thread Thomas Chang
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