Scott, I don't know if this helps you but the "normal" (Ultra)VNC service
is working fine. I can connect to the computer through this - just not
through EchoVNC.

I'll give your suggestion a try and get back to you.

For future releases I would like to be able to access the echoserver
properties through the start menu. I always hide the tray icon so it's a
bit tricky to access the echoserver properties. Just a suggestion.

Otherwise I really like the 2.0 release!

Jimmy



                                                                           
             Scott Best                                                    
             <[EMAIL PROTECTED]                                             
             om>                                                       Til 
                                       "Jimmy E. Kongskov - DATAJEK"       
             16-02-2007 17:30          <[EMAIL PROTECTED]>                    
                                                                        cc 
                                       echovnc-users@lists.sourceforge.net 
                                                                      Emne 
                                       Re: [Echovnc-users] Not connecting  
                                       at startup                          
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Jimmy:

             I suspect what has happened is that your Windows service
installation
of EchoVNC is using a different (and incorrect) password compared to the
PC which is working. The easiest thing to do is to export the echoServer
HKLM registry key from the working PC, change the login name data, and
then import that key into the non-working PC.
             The alternative solution is do de-install EchoVNC completely,
then
re-install it as a service. Reboot, then adjust the login data for
EchoVNC
via the icon running in the service tray. That usually gets the right
password
saved into the right place.
             We'll be adding a startup wizard in a future release to help
with
this. :)

             Log file wise, you can activate echoServer logging via the
main GUI.
For EchoVNC, if you add the "enablelogging" key to the echoServer
registry location for EchoVNC, and set the key to the DWORD value "1",
it will create an echoWare log file in the install folder. The exact
location
of the key should be here:

\Software\ORL\WinVNC3\EchoServers\enablelogging

             I hope that helps!

cheers,
Scott

On Feb 16, 2007, at 4:29 AM, Jimmy E. Kongskov - DATAJEK wrote:

>
> Hello!
>
> I have 2 computers where I've installed EchoVNC 2.0 on. I have a
> problem
> with 1 of them. It doesn't connect when Windows starts. It just
> have status
> disconnected when I look at the properties.
>
> This is something I've also seen with the UltraVNC echoware enabled RC
> releases. I've tried putting the UltraVNC RC10 on the computer but
> that one
> couldn't connect either.
>
> What could be the reason for that? Is there any log where I can see
> something?
>
> Is there perhaps a command I can run in a batch file to make it
> connect (as
> a temporary solution)?
>
> Have a nice weekend
>
> 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

Reply via email to