Tom, a couple of things on this... (1) you probably want to compare *all* of the registry settings on a non-working machine to a working machine. Here is the set of registry paths you need to export on an NT/2000 system. The "services" one does not exist on Win98...
Machine-general: + HKEY_LOCAL_MACHINE\SOFTWARE\ORL + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\winvnc User-specific: + HKEY_USERS\.DEFAULT\Software\ORL + under each logging on user key, you want: \Software\ORL (2) The "Install Default Reg Settings" is somewhat poorly named, in retrospect. It actually installs some customization hooks for individual users, and is not in my opinion very useful for a remote admin role since it operates under the premise that all settings are per-user. ----- Original Message ----- From: "Tom Salvitti" <[EMAIL PROTECTED]> To: "'VNC MAILING LIST'" <[EMAIL PROTECTED]> Sent: Friday, 2002-05-31 07:36 Subject: WinVNC 3.3.3 Registry Settings > Hello. I'm a new user to WinVNC and I'm hoping someone could shed some light > on something that is very confusing to me - as there seems to be no > consistency to this... > > First off WinVNC works with no problem when installed on any of my clients > (98% Win98SE/ 2% WIN 2000) so long as I don't change anything. Problem is, I > need to disable the properties and the ability to close the VNC otherwise > its too easy for a user to tamper with it. > > I found out that you should add the DWORD strings "AllowShutdown" and > "AllowProperties" to the HKEY_Local_Machine\Software\ORL\WinVNC3\Default > settings. > > The problem is of the 5 clients I'm testing the software with right now, 2 > of them work fine until you add those registry settings then they simply > don't work. A 3rd client, let's call this client "Client A", you can set the > password thru admin tools, click apply, click ok. I chose to "Install > Default Reg Settings" (because this is what I assumed made the registry > settings "appear" in RegEdit). I re-start. Go into the regedit to add > "AllowShutdown" and "AllowProperties" and there is nothing in the registry > AT ALL for WinVNC3 (at the path mentioned above). And if I go ahead and add > "AllowShutdown" and "AllowProperties" and restart...now VNC will tell me > that there is no password set and properties are locked. Huh? Password was > set before, now its magically not there anymore? > > What to be more confused? :) --- Client A is the SAME EXACT COMPUTER (same > hardware components, same OS, same software) as the two final clients that > work flawlessly W/ the registry settings edited to disallow shutdown or > tampering with the properties. > > Am I doing something wrong? Is there an order you are suppose to follow when > installing and setting up WinVNC on a client? Why all the in consistency > from machine to machine? > > Hey, sorry my post is huge an I'm asking for a lot here, but I do appreciate > it if anyone even sheds a little logic to my confusion. > > Thanks. > > -Tom > _______________________________________________ > 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
