Under Windows XP, the ForceGuest registry value is set to 1 by default in the following registry key:
On a Windows XP computer you must check:
If the Guest account is enabled, an SSPI logon will succeed as Guest for any user credentials.
If ForceGuest is disabled (set to 0), SSPI will log on as the specified user.
If the authtest util gives guest account blocked, an open guest account is detected and ms logon denies all access.
So it's important to disable ForceGuest. Otherwise all authorization is done against the guest account!
RedSackles wrote:now its works wel when using the server password having ms logon disabeld but when i enable ms logon i get the message "VNC authentication failed!"
YY wrote:RedSackles wrote:now its works wel when using the server password having ms logon disabeld but when i enable ms logon i get the message "VNC authentication failed!"
At the window of â€œMS Logon setupâ€, it mentioned that â€œLocal admins have always accessâ€, but I found there is a bug in this setting:
If all the entry of the three groups are empty, the server will reject any connection.
On the other hand, if any one of the box has something enetered â€“ EVEN IF NOT A VALID GROUP NAME, the server can accept local administrators group to logon (work as expected).
I found this problem since 1.0.2 & upto the latest 18.104.22.168, and even the beta 1.0.7.x, tested on WinXP system.
paul1149 wrote:I'm getting the same error here, with both new and old MS Logon. I'm trying to reverse-connect an XP server to a Win7 client, both on the same intranet through a router, and not getting anywhere. Using simple uVNC password works smoothly.
How did you produce the error message?paul1149 wrote:Interesting about the reverse connection not needing authentication. I didn't know that. For some reason, speccing MS Logon, whether old or new, is the make or break for connection.
Users browsing this forum: No registered users and 1 guest