I had problems with this before. Make sure the service helper is running. I have mine configured using the AuthHosts setting and had to add some keys to make this work. Originally, I wanted to prompt the user to allow connection. This didn't work when sitting at the ctrl-alt-del prompt until I added a different QuerySetting string for the System user. Under HKLM\software\orl\winvnc3 make sure you add a System user and copy anything from Default that you want to be different. I found you can tweak VNC pretty well doing this. I have QuerySetting set to 4 for Default and 2 for System. That way I can connect with VNC enter the password and be presented with the CTRL-ALT-DEL screen. For some reason I also had to manually add the service helper to the HKCU\software\Microsoft\windows\current version\run. I added WinVNC string with value of "C:\program files\orl\vnc\winvnc.exe" -servicehelper. (with the Quotes) This allows VNC to use the system account when no one is logged on. For instance, I also like the locksetting key which is set so that if the remote user tries to kill the session while I am logged in as administrator, the machine will automagically log out the administrator for me. As pointed out in a post earlier this week, if you just set this in Default under the key listed above, you will log any user off after you help them. This almost defeats the usefulness of this tool. If I am trying to save time by helping the user remotely and then I log them off. That is another 5 minutes until they are productive again. Solution: Add a key under WinVnc3 that matches your admin account or any account that you want to treat differently. I add administrator, set the lockSetting under this and system (just in case) and don't set it under default. Result: If the session is killed or quit under administrator, the 2000 pro machine will automagically log off. For normal users, if the same thing happens, they get to continue working. What can I say... I have remote users with a lot of time on their hands. I had to lock this up the best that I could with out losing the ability to log on as a local admin to the box and not get caught leaving it that way. I hope this rambling helps you or anyone else. If I misses something, someone please correct me. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 12, 2001 10:00 PM To: [EMAIL PROTECTED] Subject: vnc-list-digest V1 #1198 vnc-list-digest Friday, July 13 2001 Volume 01 : Number 1198 Date: Thu, 12 Jul 2001 11:04:22 +0200 From: Reinhold Biedermann <[EMAIL PROTECTED]> Subject: VNC as service under Win2000 Hello, I succeeded to install the latest WinVNC as service under Windows2000 Professional. Nevertheless I'm only able to start a remote VNCviewer when somebody is logged in under Win2000. If nobody is logged in (p.e. Win2000 is showing the login-shell) this is not possible. Does anybody of you have experience with this kind of problem concer- ning WinVNC as service under Windows2000? So far, I didn't find any information about this in the docu's, mailing list, faq's! Thanks in advance, please also reply to [EMAIL PROTECTED] Reinhold ========================================================== Ein Service von bingo e.V. - http://webmail.bingo-ev.de/ Internet KnowHow ist bingo e.V. ========================================================== ------------------------------ --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to [EMAIL PROTECTED] See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
