I'm still having some problems getting some computers connected at startup.
I suspect it could be because of bad internet connection. I mean if the
computer isn't fully connected to the network and internet when echovnc
tries to connect to the echoserver.
Is there any way to make a bat file which uses the same command to connect
to the echoserver as the echovnc gui? The problem is my users don't have
access the echoserver properties as the icon in the taskbar is hidden.
Therefore I would like to put a bat file on the their desktops so if they
activate that it will try and reconnect to the echoserver?
Is that possible?
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
