Hey everyone,
I've got a bit of a situation with my domain network after upgrading from Windows 10 to Windows 11. We set up new Windows 11 PCs, and one of them has a shared printer that was working fine until recently. Now, I keep getting a prompt for network credentials whenever I try to authenticate with the other PCs, but none of the credentials seem to work—I've tried local admin accounts, domain admin accounts, and even IP and hostname connections to no avail.
What's strange is that all the PCs can still authenticate with the domain controller without issues, and I can also connect to the shared resources from the DC to any of the PCs. I've looked at the DNS settings, tried using the Credentials Manager, and logged in with both local and domain accounts. The only error I'm seeing in the event logs is "ID 6167, Source LSA: There is a partial mismatch in the machine ID. This indicates that the ticket has either been manipulated or it belongs to a different boot session. Failing authentication." So far, everything else seems fine—no domain trust issues. Has anyone encountered this problem before, or have any ideas what might be causing it?
By the way, no PCs were cloned during setup, so I'm stumped as to why this ID 6167 keeps popping up in the logs.
4 Answers
Also, don't forget to check if network discovery is enabled on all PCs and ensure that RPC (Remote Procedure Call) is allowed. Sometimes, simple settings like those can block authentication processes.
Yeah, it's always the little things that trip you up. Double-check those settings!
It sounds like you might have a problem with duplicate machine SIDs. If a custom image was used during setup but wasn't properly prepared with sysprep, it could cause issues like this. You should check the SIDs for those PCs. Here's how you can do it: open the command line and run `reg query HKLMSOFTWAREMicrosoftCryptography /v MachineGuid`. That will tell you if they share the same SID, which could be where your authentication problem is stemming from.
Oh wow, I just checked mine, and they are identical! Thanks for the tip!
You might want to consider removing them from the domain, running sysprep, and then rejoining. That should clear up the SID issues.
If you're still having trouble after checking the SIDs and settings, and if these machines are sourced from a specific vendor, they may have imaging issues. It could be worth reaching out to the vendor for guidance if things don't improve.
I can relate; I've faced this with several mini PCs in the past. Even if everything else looks good, sometimes the underlying configurations from the vendor can mess with procedures.
Great call! I remember running into similar issues because of network discovery being turned off.