unable to connect to host: Connection timed out (10060)

[Scott C. Best]

Boi1der:

 	Sorry to hear that Comcast has gotten so stringent.
It's about as bad -- and perhaps as necessary -- as WinXP-SP2
changing the default on the builtin Windows firewall from
disabled to enabled.

 	As John indicated though, as long as Comcast is still
allowing you unfettered *outbound* connections, EchoVNC will
still allow you to access to RealVNC servers. You'll have to
utilize an echoServer that's not restricted by Comcast, of
course, such as the free demo one we're running. EchoServers
are also easy enough to get setup on really inexpensive hosted
servers such as Linode.

cheers,
Scott

> I can see it from their point of view, but
> unfortunately, it interferes with our freedom of
> remote access! :-)
>
> --- John Aldrich <JAldrich "at" covista.com> wrote:
>
>> You might be able to use EchoVNC which might allow
>> you to bypass Comcast's
>> filters. Look at it from their perspective... up
>> until recently a lot of
>> their clients' PCs had become zombie spam servers.
>> Now they are cracking
>> down on running ANY kind of server to help keep YOUR
>> PC safe!
>> 	John
>>
>> -----Original Message-----
>> From: boi1der [mailto:boi1der "at" yahoo.com]
>> Sent: Tuesday, July 19, 2005 11:39 AM
>> To: vnc-list "at" realvnc.com
>> Subject: unable to connect to host: Connection timed
>> out (10060)
>>
>>
>> I'm a newbie to the list, but I just found out that
>> since I'm using Comcast as my ISP, without a static
>> IP
>> address, Comcast won't allow any FTP, Ping, or any
>> type of traffic to the IP address of my firewall. So I
>> can't even open a port to allow the traffic through to
>> the VNC server. So unless you want to buy a fixed IP
>> address from Comcast, you can't run the software.