I had a problem using the MS logon feature of RC18. I installed the MSLogon v.2 fix and that fixed the problem.
UltraVNC Server: Windows 2000 Professional, SP4
Domain: local workgroup
Problem - this event appears on the server whenever an UltraVNC authentication is attempted. But the VNC connection works anyway:
EVENT # 3707
EVENT LOG Security
EVENT TYPE Audit Failure
SOURCE Security
CATEGORY Account Logon
EVENT ID 681
USERNAME NT AUTHORITY\SYSTEM
COMPUTERNAME COMPNAME
TIME 8/23/2004 9:17:51 PM
MESSAGE The logon to account: isdiua
by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
from workstation: COMPNAME
failed. The error code was: 3221225572
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
MS Logon problems with 1.0.0 RC 18 - fixed
The message you got with the "old" ms-logon is not a failure but intended. It checks for an open Guest account which will allow attempts with wrong username/password combinations to succeed under WinXP.
The new ms-logon works differently by impersonating the authenticated user and then check the authorization, i.e. group membership.
As long as the Guest account is not used for one of the groups there should be no problem.
The new ms-logon works differently by impersonating the authenticated user and then check the authorization, i.e. group membership.
As long as the Guest account is not used for one of the groups there should be no problem.
BobBabai:
I had some issues with MS LOGON included in RC18.
Users in 'USERS' group had complete access once logged in, instead of having ReadOnly access.
Now, after installed MSLogon v2 it works perfect. :-o
You can download here:
ultravnc-newMSlogon-2.zip http://dl.ultravnc.net
It is explained in this topic:
[topic=637][/topic]
UltraVNC rocks. Is the best vnc server/client i've tried.
Thanks Marscha.
I had some issues with MS LOGON included in RC18.
Users in 'USERS' group had complete access once logged in, instead of having ReadOnly access.
Now, after installed MSLogon v2 it works perfect. :-o
You can download here:
ultravnc-newMSlogon-2.zip http://dl.ultravnc.net
It is explained in this topic:
[topic=637][/topic]
UltraVNC rocks. Is the best vnc server/client i've tried.
Thanks Marscha.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact: