Ayup, that would do it. :) EchoWare will support both HTTP
connect-style proxies, as well as SOCKS4/5. We're about a month
away from completing that update.
cheers,
Scott
On Jun 23, 2005, at 11:30 PM, <[EMAIL PROTECTED]> wrote:
Oh, I forgot, I am using a modified version of Stunnel which handles
HTTP Connect-style proxies:
http://www.stunnel.org/patches/desc/connect-proxy.mwald.html
----- Original Message ----- From: <[EMAIL PROTECTED]>
To: "Scott Best" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Friday, June 24, 2005 9:19 AM
Subject: Re: [Echovnc-users] Screensaver problem
Scott,
Thanks for the reply.
One more thing: The only way I can connect to echoserver at home is
using Stunnel through port 443 because echoVNC with libeay32.dll
cannot connect directly through port 443 for some reason.
any comments on this?
thank you.
Gurhan
----- Original Message ----- From: "Scott Best" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Thursday, June 23, 2005 7:26 PM
Subject: Re: [Echovnc-users] Screensaver problem
Gurhan:
Heya. Yes, EchoVNC has a problem recovering from a "locked
PC" right now. It should, of course, auto-reconnect to the echoServer
in the same way that it will when you stop and then restart the
echoServer. We're looking into why it's not...
-Scott
On Jun 23, 2005, at 8:41 AM, <[EMAIL PROTECTED]> wrote:
Hi there,
First of all, thanks for providing this software.
My main aim is to connect to my work PC from my home PC.
This is my setup on 2 WinXP computers:
1- I am running echoServer 1.40 and echoVNC 1.33 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- The work PC connects to the echoserver at home successfully
through port 443.
4- I can sucessfully connect to work PC from my home PC when the
work PC is NOT running a screensaver.
5- As soon as the work PC activates the screensaver, the echovnc
installed on this PC disconnects from the echoserver and thereby
making it impossible to make a connection ever again.
6- The problem can only be solved by deactivating the screensaver
on work PC, logging in, AND deleting and creating a new echoServer
connection in the EchoServer tab BECAUSE the EchoVNC on the work PC
DOES NOT try to reconnect automatically from this point on.
Any ideas about how to overcome this frustration?
thank you,
Gurhan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
