I saw this question in a search to find a related answer.

Dear all,

    I'd put the command-line:
    (full-path)\winvnc -connect < listening-client's ip>
in the schedule-task and set the job to be run at system boot. But no
connection is made.

    However, it can connect after the user login if I put the command-line
in startup
folder. Besides, it can be connected by the remote VNC client before the
login screen.

What should I do? Pease help, thanks!!!

An answer is:


Using regedit I found the WinVNC service under [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\winvnc] I exported that to a .reg file and edited the "winvnc" strings to be winvnc2. Then I imported that and used regedit to change the -service in the key to be -connect 172.16.4.3 (Obviously this will be different for you)

There is a security key. I have no idea what it is specifically. I just used a copy the one in my existing WinVNC service key ...

Hope this helps you!
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to