Hi Scott!
OK, I think I have to try the new 2.0 version some time soon.
I actually used your UltraVNC-ew-1.02-RC10 to solved the problem. The RC10
seems to work much better than earlier. I coudn't get those to connect to
the echoserver everytime UltraVNC started.
This way I can make echovnc run as a service along with UltraVNC and don't
have to use srvany to configure a service anymore. Really great app!
Jimmy
Scott Best
<[EMAIL PROTECTED]
om> Til
"Jimmy E. Kongskov - DATAJEK"
13-02-2007 16:40 <[EMAIL PROTECTED]>
cc
echovnc-users@lists.sourceforge.net
Emne
Re: [Echovnc-users] Vedr.: Re:
EchoVNC on Windows 2003
Jimmy:
Good point: in the 1.4 release, EchoVNC "searches" for a VNC
server
to use in the 5900-5909 port range. In the 2.0 release, since it's
all integrated
now, you can use any port number.
cheers,
Scott
On Feb 13, 2007, at 12:00 AM, Jimmy E. Kongskov - DATAJEK wrote:
> OK, thanks! I found out what was "problem". Apprantly EchoVNC can't
> find
> the VNC server if it's using port 5910. If I just choose 5900 then
> it's
> working.
>
> Can ports from 5900-5909 only be used?
>
> Jimmy
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
