MS-Logon Feedback on WXP SP1

LouisJJames · Post by **LouisJJames** » 2004-09-23 02:17

In my third install of the new MS Logon-2, I did run into some difficulities. I hope this info might help:

1.- The Host Machine is Windows XP Pro SP1
2.- Using the DSM Plugin with Key previously generated and copied
3.- Installed the MS Logon-2 per instructions
4.- If NewMSLogon is set to 1, I get the error message VNC authentication failed!
5.- Changed NewMSLogon and set it to 0, and I get in without a problem.

At the same site, I have another WXP Pro set up indentically and it works great. Hmm

Any thoughts would be kindly appreciated. At this time I have it set to "0" so I can service the machine.

A SUGGESTION: It would be nice if there was a way to know which MS Logon I was using. At least until you feel confident of the module. Maybe a dialog box or something just to know. Just a thought.

Louis James

Marscha · Post by **Marscha** » 2004-09-23 07:25

LouisJJames,

Thanks for your response.
Maybe you can try to get it working without DSM Plugin, just to test mslogon.

I agree that it would be nice to have some hint which mslogon is used.
The problem is that you need this info at the client side. This can't be implemented without changing the protocol.
My goal is to eventually replace the "old" mslogon completely

But I understand that this could lead to irritations in the meantime.
I'll try to implement better debug information so that it's easier to track down errors/misconfigurations.

Martin

LouisJJames · Post by **LouisJJames** » 2004-09-23 12:14

Martin:

As you suggested, I did try to logon without the DSM Plugin but it did not work. This is what happened:

1.- Went to Regedit and changed NewMSLogon to 1
2.- Went to the User Settings and unchecked the DSM Plugin
3.- At this point, I disconnected
4.- Reconnected and got the logon (Username and Password)
5.- After entering the logon info, I get the error message VNC authentication failed!

Then the system locked. I have PCAnywhere set up temporarily until UltraVNC is stabilized. I remoted in using PCA and found that UltraVNC "crashed".

At this point, (using PCA), I made sure that both the Default and user settings have the DSM Plugin unchecked. To make sure, I also went into the registry and found the UseDSMPlugin entry set to 0 in both areas (WinVNC3 and WinVNC3\Default). I rebooted the system.

Unfortunately it did not work. I remoted again using PCA, checked the NewMSLogon to 0. I disconnected from PCA and connected with no problem using UltraVNC.

I wonder if I should reinstall all of UltraVNC. However, I must say that UltraVNC is working without the New MS Logon 2.

One interesting thing to note about this computer. It was slammed with the W32.NetskyC worm and had a lot of spyware. The system was cleaned from both. And the system seems to be working well without any problems except for what we are discussing with UltraVNC. I don't think the Netsky worm or spyware could cause a problem but it's a thought.

I also wonder if some temp files are created by UltraVNC in the C:\Documents and Settings\username\Local Settings\Temp folder. I found a lot of files here. Just a thought.

Look forward to hearing your thoughts.

Louis James