The Proxy is the same Linux machine that the EchoServer is running on.
So it would be EchoVNC Viewer -> Proxy/echoServer -> EchoVNC Server
There is one thing I should note. The echoServer is running on port 21.
This is because one of the networks I plan to connect from blocks most of
the outgoing ports.
Mark
On Jan 15, 2008 8:45 PM, Scott Best <[EMAIL PROTECTED]> wrote:
> Mark:
>
> Hello! Sorry, I'm not sure I see where in between the EchoVNC
> application and the echoServer you inserted a new Proxy connection...
>
> Is it:
>
> EchoVNC Viewer -> Proxy -> echoServer <- EchoVNC Server
>
> Or ... ?
>
> thanks,
> Scott
>
> On Jan 15, 2008, at 5:46 PM, Mark Rhoades wrote:
>
> > I have found an interesting solution to the slowness problem.
> >
> > I created a SSH tunnel to my Linux box. Setup EchoVNC Viewer to use
> > the proxy connection.
> > Then it connected to the EchoServer and worked fine. If I remove the
> > Proxy connection it is unusable.
> > I tried this several time and I have no doubt this was the solution.
> >
> > Any ideas as to why?
> > I would really like to use it without the proxy connection.
> >
> > Mark
> >
> > On Jan 14, 2008 8:16 AM, Mark Rhoades < [EMAIL PROTECTED]> wrote:
> > I thought about that yesterday and was going to try it but didn't
> > find the correct information for the demo server. I found
> > demo.echovnc.com:1328
> >
> > I will give that a try.
> >
> >
> > On Jan 14, 2008 6:44 AM, Scott Best <[EMAIL PROTECTED]> wrote:
> > Mark:
> >
> > I'm not sure that this will affect your results much, but the
> > latest
> > build of EchoVNC is version 2.32, which you can get here:
> >
> > http://www.echogent.com/download_echovnc.htm
> >
> > Also, do you see the same problem when connected to our
> > demo echoServer? Please try "demo2.echovnc.com ", with the
> > password "demo2008". That will help isolate where the issue could
> > be.
> >
> > cheers,
> > Scott
> >
> > On Jan 13, 2008, at 11:28 PM, Mark Rhoades wrote:
> >
> > > The EchoServer is 1.61
> > >
> > > EchoVNC is 2.20 according to the Exe version stamp under windows.
> > >
> > > On Jan 13, 2008 9:08 PM, Scott Best < [EMAIL PROTECTED] > wrote:
> > > Mark:
> > >
> > > Hello! Those are some surprising results. I expect the
> > relayed
> > > connection
> > > to be a *little* slower, but not *broken* slower. Exactly what
> > version
> > > of EchoVNC,
> > > echoServer, and Windows OS are you running?
> > >
> > > -Scott
> > >
> > > On Jan 11, 2008, at 7:54 AM, Mark Rhoades wrote:
> > >
> > > > Hello all,
> > > >
> > > > I am hope somebody can help me with this problem. I have tried all
> > > > kinds of setting in EchoVNC to try and get this to work.
> > > >
> > > > I have a EchoServer setup on a linux box (hosted Virtual Private
> > > > Server).
> > > > The remote computers can connect to the EchoServer.
> > > > I can can see them an initiate a connection.
> > > > It asks for the password and then starts to show the remote
> > screen.
> > > > I get about 1/6th of the screen fairly quickly
> > > > The rest of the screen either never shows up or takes a very long
> > > > time to display (10 minutes or longer).
> > > >
> > > > All of the sites are on high speed broadband.
> > > >
> > > > I am on a 15meg x 2meg connection
> > > > EchoServer is on a 1meg x 1meg connection
> > > > Remote site is on a 512k x 512k connection
> > > >
> > > > I have been able to connect point to point eliminating the
> > > > EchoServer and everything works well.
> > > > Once the EchoServer is in place there is extreme slowness.
> > > >
> > > > Any ideas on how to solve this?
> > > >
> > > > Thanks,
> > > > Mark
> > >
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
