Steve, That got it. Thanks very much.
It would be helpful if the setup program had a choice to install the service for a single user or all users. By the way, for a few days I have been running the bug fix mods posted by Mike Smith. Thanks Mike! It does seem faster (at least on my network) than the older versions that I have been running and it has not given me any problems. But I must note that I have used it only on Win2K. Leonard -----Original Message----- From: Steve Palocz [mailto:[EMAIL PROTECTED] Sent: Friday, February 21, 2003 11:59 AM To: 'Leonard Tiritilli' Subject: RE: Reboot & Logon to remote machine. Leonard, Basically you are only setting the current user settings. The default settings are confused, so when the user logs off, his settings are no longer being used, so it closes connection. Easy fix. Leave service running Open regedit Delete hkey_currentuser/software/orl/winvnc3 Next click start, programs, realvnc, server, show default settings. Set the password. And then restart the service. All should be fine now. Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leonard Tiritilli Sent: Friday, February 21, 2003 12:50 PM To: [EMAIL PROTECTED] Subject: RE: Reboot & Logon to remote machine. I agree that it is behaving as though VNC is running in the app mode. But when I ran setup I chose to have the service installed. When the system boots up the service is running and I have checked services and found that the VNC service is running with automatic startup as a local system account. The path to executable is shown as "C:\Program Files\RealVNC\WinVNC\WinVNC.exe" -service. But all I need to do is log off and any existing VNC connection is killed and the machine cannot be accessed until someone (anyone) logs on. This condition exists on every Win2K installation to which I connect. Is there something else that I should do to install VNC as a service? Is there a registry entry that I should check and edit? Or is there some way to prioritize the initialization of the service? Leonard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Carl Sent: Thursday, February 20, 2003 6:07 PM To: VNC Subject: Re: Reboot & Logon to remote machine. Yes. If VNC is running as a service on the remote machine it will restart when the machine restarts. Then you should be able to login again. Sounds like it's running as an app on the w2k machine. Carl ----- Original Message ----- From: "Leonard Tiritilli" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 20, 2003 5:05 PM Subject: Reboot & Logon to remote machine. > I recall restarting a remote machine (probably a Win98 machine) and being > able to use VNC to reconnect to the remote machine (after allowing enough > time for it to reboot) and logon. If I simply logoff or restart the current > user on a remote Win2K machine VNC disconnects and I cannot reconnect to the > machine. This behavior has been normal with all versions that I have used > over at least the past year. > > I am now running version 3.3.6 on Win2K machines. I am running VNC as > service with automatic startup as a local system account. Is there a way to > reboot and logon to a remote Win2K machine? > > Leonard > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
