Hi there,

I think I found the problem/request:

This is my setup on 2 WinXP computers:
1- I am running echoServer 1.40 and echoVNC 1.40 on my Home PC which 
is accessible on all ports.
2- Work PC is behind a firewall which allows ports 443 and 80 only.
3- I can sucessfully connect to work PC from my home PC using the modified 
TightVNC, which is 
registered as a system service on both PCs. This modified tightvnc solved the 
screensaver 
problem!! :)


I think, the problem comes from stunnel itself. it loses the connection, 
thereby cutting the 
communicaiton between home and work pc's.

The http proxy at work requires a SSL connection thru port 443.

therefore, is there a way to connect echovnc OR the modified tightvnc using an 
integrated SSL?

Thank you again.

Gurhan

****************************************************************
2005-08-10 09:51  
Dear Scott,

I am really excited about this project so here I am trying to let you know 
about the problems I have:

Unfortunately, due to some reason I am not sure about, Echovnc does NOT try 
to reconnect to the echoserver. Apart from the reason why there is a 
disconnection, I would love to see echovnc try to connect over and over 
again until there is a connection in place. Would that be possible?

btw, my diagnosis is that the connection is lost once the computer (winxp) 
is locked followed by the activation of the screensaver.

Looking forward to hearing from you soon.

Regards,

Gurhan


> ----- Original Message ----- 
> From: "Scott C. Best" 
> To: 
> Cc: ; ; 
> 
> Sent: Monday, August 08, 2005 9:37 PM
> Subject: EchoVNC-1.40PRE01 available
>
>
>>
>>  Heyaz. The first pre-release of the 1.40 version of
>> EchoVNC is now available. This is the first application to use
>> the 1.60 version of echoWare, which now supports connections
>> via HTTP and SOCKS proxies.
>>
>>  For those of you trying to use EchoVNC from clients
>> that are behind firewalls *and* web proxies, I would very much
>> appreciate any feedback about the added proxy support. It passes
>> our testing here (HTTP, SOCKS4, SOCKS5 with/w.o. passwords),
>> but nothing beats real-world data.
>>
>>  Installer is here:
>>
>> ftp://ftp.echogent.com/EchoVNC/EchoVNC_1.40PRE01_Setup.exe
>>
>> thanks,
>> Scott
>>
>>
> 

                        

 


From: Scott C. Best <[EMAIL PROTECTED]> 
 Re: Re: EchoVNC-1.40PRE01 available   
2005-08-10 12:09  
Gurhan:

        Here would be a very useful experiment: run EchoVNC
on the WinXP PC on your LAN, and run the Windows echoServer on
another PC on your LAN. Connect, then let the WinXP PC "fall
asleep" so the screensave activates. On the echoServer side,
does the connection fail?

        If EchoVNC connects successfully to an echoserver, its
"auto-reconnect" status gets automatically enabled. That status
*should* reset only if EchoVNC tries to connect and gets a failed
password response.

        Please let me know what that above experiment shows
for you...

thanks,
Scott

On Wed, 10 Aug 2005 [EMAIL PROTECTED] wrote:

> Dear Scott,
>
> I am really excited about this project so here I am trying to let you know 
> about the problems I have:
>
> Unfortunately, due to some reason I am not sure about, Echovnc does NOT try 
> to reconnect to the echoserver. Apart from the reason why there is a 
> disconnection, I would love to see echovnc try to connect over and over again 
> until there is a connection in place. Would that be possible?
>
> btw, my diagnosis is that the connection is lost once the computer (winxp) is 
> locked followed by the activation of the screensaver.
>
> Looking forward to hearing from you soon.
>
> Regards,
>
> Gurhan
>
>
>> ----- Original Message ----- From: "Scott C. Best" 
>> To: 
>> Cc: ; ; 
>> 
>> Sent: Monday, August 08, 2005 9:37 PM
>> Subject: EchoVNC-1.40PRE01 available
>> 
>> 
>>> 
>>>  Heyaz. The first pre-release of the 1.40 version of
>>> EchoVNC is now available. This is the first application to use
>>> the 1.60 version of echoWare, which now supports connections
>>> via HTTP and SOCKS proxies.
>>> 
>>>  For those of you trying to use EchoVNC from clients
>>> that are behind firewalls *and* web proxies, I would very much
>>> appreciate any feedback about the added proxy support. It passes
>>> our testing here (HTTP, SOCKS4, SOCKS5 with/w.o. passwords),
>>> but nothing beats real-world data.
>>> 
>>>  Installer is here:
>>> 
>>> ftp://ftp.echogent.com/EchoVNC/EchoVNC_1.40PRE01_Setup.exe
>>> 
>>> thanks,
>>> Scott
 




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users

Reply via email to