Floyd, I've had it perform flawlessly so far, but I've done clean installs after nuking everything VNCish in the registry. The methodology I have used is below.
When I go back and check, I see that the only user-specific data is a VNCHooks key; all of the connection config data is under HKLM\SOFTWARE\ORL\WinVNC3\Default ================================ ================ Test Platform Windows 2000 SP3 TS in licensed Application Mode. (System was actually a VMware machine) ================ Install Process (1) Manually did a "change user /install" since I prefer controlling the entire process (and this ensures that it stays in install mode until I say stop). (2) Did the default install with the following 2 modifications on the "Select Additional Tasks" screen: + checked "Register as a service" + checked "start the service" (3) After setup completed, the service window launched and I set the password. (4) switched to execute mode with "change user /execute". ================= Post-Install Testing I was immediately able to connect successfully to the console session with no one logged on and with one other user logged on remotely. Logging on to the console directly first and then opening VNC and connecting worked fine as well. I powered the machine down completely, then restarted. VNC access was available moments after the Ctl-Alt-Del screen popped up on the VMware virtual console. Again, no issues with logging on. On Tuesday, 2002-10-01 14:12 [GMT+0100=CET], Floyd Russell <[EMAIL PROTECTED]> wrote: > Has anyone else run across a problem with some machines running > terminal services not working with vnc 3.3.4 as a service? I have > some machines where > 3.3.4 will install just fine, and run as a service and give me console > access. Others will only run as the user, when I try and run the > service clients get an error message about the password not being > set. However, if you run the server and set the password clients can > then connect, but only to the virtual desktop not the real console. > All machines are configured the same as far as terminal services are > concerned, and are all at the same service pack/hotfix levels. Any > help appreciated. Oh, and trying to use my old method of; stop > service, run server, set default properties, kill server, start > service doesn't work. I still get the password not set error. > > Thanks, > Floyd R. > _______________________________________________ > 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
