I have installed Ultr@VNC 1.0.1 on a Windows 2000 SP4 server and on my WinXP SP1 workstation, configured the server to use MS-Logon II, defaulting to allow the local administrators group full access.
The Active Directory 2000 Domain Admins group has been added to the local administrators group of this server.
Yet, when I connect to this server and use my domain admin credentials, I get this error in the server's Security Event Log:
Date: '12/9/2005'
Time: '1:29:00 PM'
Event: '681'
Type: 'AUDIT FAILURE'
Category: 'Account Logon '
User: 'NT AUTHORITY\SYSTEM'
Source: 'Security'
Computer: 'STNTS27'
Message: 'The logon to account: WOODSML by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: STNTS27 failed. The error code was: 3221225572 '
Data: ''
It still lets me on and I can do what I need to do, that's not the issue.
Just need to know why this error is generated, and if there's a fix/change that needs to be made to make it stop.
Thanks.
Mark L. Woods
The Solae Company
St. Louis, Missouri USA
After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-14: 1.7.1.X-dev release builds need tests and feedback: https://forum.uvnc.com/viewtopic.php?t=38134
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-14: 1.7.1.X-dev release builds need tests and feedback: https://forum.uvnc.com/viewtopic.php?t=38134
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome
MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
it's not a bug, it's a feature
Now, seriously: When authenticating to VNC, you specified your username and password, but not your domain.
Windows assumes that this is a local account and tries to authenticate "Workstation\Username" which fails.
The next guess is "Domain\Username" which succeeds.
To prevent the "error" you have to specify the fully qualified name when vnc authenticating:
Either domain\username or username@domain.com (or something similar, that's your UPN, user principal name).
Now, seriously: When authenticating to VNC, you specified your username and password, but not your domain.
Windows assumes that this is a local account and tries to authenticate "Workstation\Username" which fails.
The next guess is "Domain\Username" which succeeds.
To prevent the "error" you have to specify the fully qualified name when vnc authenticating:
Either domain\username or username@domain.com (or something similar, that's your UPN, user principal name).
