Server 2003 Authentication

[loudog]

I am having the worst time trying to figure out why this is happening..


I installed UVNC on a Windows 2003 SP1 Server and here is the situation:

Installed as a service:
If I try to connect to the UVNC server, it tells me there is no password set. I go through all the steps to set a password and reset a password, but it will not work.

INstalled NOT as a service:
Works pserfectly fine as olng as SOMEONE is logged on to the server at all times....not exactly practical.

This is happening on all of our S2K3SP1 servers.


Any ideas?

[bevtech]

Install it as service..

[loudog]

I did that.... the connection fails every time. I cannot figure out why the serve rwill not hold a password. I have even tried using Windows authentication and it still fails telling me there is no password set.

[bevtech]

oh... your password will not stay..

Did you try to uninstall reboot reinstall make sure to clean out old registry settings is checked. Then place the password in at that time. You will still n eed a classic password eventhough you want to use mslogon..

[redge]

Installed as a service:
If I try to connect to the UVNC server, it tells me there is no password set. I go through all the steps to set a password and reset a password, but it will not work.

...why use UltraVNC if it cannot be installed to start alone?

Anyway until you will make a fix for this I think I found a way to set it up using remote desktop:
1. Start UltraVNC server and setup the password and other settings for UltraVNC application.
2. Setup the password and other settings for Show Default Settings from UltraVNC server menu (from start menu)
3. With regedit copy the Password key from HKEY_CURRENT_USER/Software/ORL/Winvnc3 to HKEY_LOCAL_MACHINE/Software/ORL/WinVNC3. (actually you need to create a new binary key at destination and copy only the value)

Only doing this the UltraVNC will start automatically when you restart the computer.
I think the bug is that when you set the password HKEY_LOCAL_MACHINE is not updated cause there is not password key there but only in HKEY_LOCAL_USER.
Maybe you can fix this for the future and include these advices in the manual until then.

Thanks for your advice - I was having the same problem - I had to copy the whole of HKEY_CURRENT_USER/Software/ORL/Winvnc3 to HKEY_LOCAL_MACHINE/Software/ORL/WinVNC3/Default
for mine to work (version 1.0.1).

related topic
[topic=3901][/topic]

[bilbus]

did you install it while connected to remote desktop/TS?

if you did thats your problem... connect to the local console

[rmoller]

I beg to differ! DO NOT connect to the local console with RDP/TS! That is, DO NOT use mstsc /CONSOLE /V:server ! VNC is not compatible with servers who "have suffered" RDP/TS connect to local console.

I have no problems installing Ultravnc as service (and mirror driver) from remote desktop/TS - if I first populate HKEY_LOCAL_MACHINE/Software/ORL/WinVNC3 with the Password entry copied from another installation.

I have first installed Ultravnc as service on my local PC and configured default password. Then I export HKEY_LOCAL_MACHINE/Software/ORL/WinVNC3 from regedit to a flat file. This file can be copied to the RDP/TS server and imported with regedit. Once this is done, UltraVNC can be installed normally as service, and it will be ready to connect to with VNCviewer and the same default password as the original local PC. Then you can change password/auth.