Hi
I see the following errors on all my VM servers that have VMware tools installed
User sacnmclpvc001@cnm.lan logon attempt into computer '127.0.0.1' failed due to 'Unknown user name or bad password.'
My Adaudith Plus program tells me it comes from the following program
Caller process name is
C: \ Program Files \ VMware \ VMware Tools \ vmtoolsd.exe
Has anyone seen this error
Regards Mogens Westergaard
Hey, hope you are doing fine.
Are we speaking oh vSphere ESXi VMs right?
On Workstation you have something called autologin. but this might not be the case.
this user sacnmclpvc001@cnm.lan has something to do with a vSphere / vCenter admin?
This event is a Windows event ID that I can see on our Windows domain controllers.
Do I understand your question correctly. We are running on a ESX platform with a lots of VM's
Regards Mogens
It is Windows Event ID 4625. It looks like it coming local from every VMserver
Okay , can you check here?
https://www.vcloudnine.de/event-4625-failure-reason-domain-sid-inconsistent/
Is it possible that the VMs were deployed as templates but not sysprepped/quickprepped?
Here is the whole error messages from the local VM machine
I will talk to the Windows team tomorrow
Thank a lot for you feedback
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: Server name$
Account Domain: xx
Logon ID: 0x3E7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: sacnmclpvc001@cnm.lan
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0xa1c
Caller Process Name: C:\Program Files\VMware\VMware Tools\vmtoolsd.exe
Network Information:
Workstation Name: xxx
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Okay, my guess is the following:
sacnmclpvc001@cnm.lan is being used as the service account for vmware tools and it's password has changed recently.
can you confirm if VMware tools are running with that account?
Lookinf forward to hearing from you
No. Vmware tools is running as Local system
Regards Mogens
Moderator: Thread moved to the Virtual Machine, Guest OS and VM Tools area.
Problem is not solved
Having the same issue over here.
The tools are failing to log on as administrator.
Checked thinking the systems may have had different computer SIDs but no.
Any one find a solution here?
Hi
The issue was resolved a few days ago
Our service provider has solved the problem
It is a reporting tool that tries to log on
I just need to find out what the product is called
Then I write again
Regards Mogens
Hi
Last word in this case
It was CloudPhysics which gave the problem
The problem is reported to the vendor, to find a solution so the tool does not try to log on to vms.
Thanks for the input
Regards Mogens
Did you find out what was the issue, I'm having the same issue, but I think it is my backup software, even though my backups are completing fine. Did they correct the issue or give you a fix to apply?
Regards Dave