MS-Logon 2 Works but Questions Exist

LouisJJames · Post by **LouisJJames** » 2004-09-22 02:43

I just installed the MS-Logon 2 on a system and followed the step-by-step instructions including:

*.-UltraVNC RC18 was already installed
*.- Stop the ultravnc service.
*.- Add a DWORD regkey HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\NewMSLogon = 1
*.- Made sure In WinVNC Properties check "Require MS-Logon".
*.- Configured a group called VNC (administrator is in the group) and added the fully qualified name 'meredith\vnc' (Meredith is the computer name)
*.- Stopped the Ultravnc service
*.- Replace winvnc.exe in the installation dir
*.- Add authSSP.dll to the installation dir
*.- Start the ultravnc service.

Everything worked perfectly well (Frankly I was not having problems before). However, I tried to save the connection (Save Connection Info as...) The file saved but when I tried to used that file to connect, I get the error message "VNC Authentication failed". Now I know that I can "turn off" the MS-Logon and that would resolve the problem. However, is MS-Logon 2 suppose to address this?

Or can a line be added to the saved connection file that would have the user name. I see the password in the file (hex). If so, what is the line to enter?

Did I see any difference? If MS-Logon 2 is intended to speed up the authentication, it seems to be doing the work. I was having a problem with this particular machine in that it authenticated and just sat there. Sometimes the server would then crash. Since I have installed the MS-Logon 2 update, that problem seems to have gone away. It logons on more quickly.

However, I manage a lot of machines. Having to remember and type the vnc server name, the user name and password for each can be interesting. It would be nice to have this all in a vnc file that I can just double-click. But I do want to use the ms-logon requirements. (I know, I want my cake and eat it too).

UltraVNC is awesome! Look forward to hearing from you.

Louis James

Marscha · Post by **Marscha** » 2004-09-22 08:23

The main intention of mslogon2 is to provide MS logon authentication with support for multiple domains.
Once mslogon2 is stable and reliable I'll consider addressing the issue with saving the username in the connection info.

LouisJJames · Post by **LouisJJames** » 2004-09-22 10:58

Thanks for the quick reply.... I plan to incorporate MS-Logon 2 as part of all my installs. Here's my vote for hoping you can address adding the username as part of the connection info. That would be wonderful.

Thanks again!