I'm working at a managed service provider and one of my clients has several local SMB shares used by their clinic's computers. After every update, they encounter issues where it says "Incorrect Network Password" or "username/password incorrect", despite confirming the credentials multiple times. This requires me to roll back the security updates frequently, which is frustrating. The latest issue came up with update KB5068861. Our admin just blacklists the patch, but I'm looking for a more permanent solution. They aren't willing to spend money on new equipment, and setting up something like a NAS worries me since I think it could just recreate the same problems. I've suggested alternatives like SharePoint or Azure Files, but they're concerned about their X-ray machine's ability to connect to the network share. Any advice would really help!
3 Answers
Your suggestion of migrating to SharePoint or Azure Files sounds a bit misguided. It’s frustrating that Microsoft’s updates are breaking basic file sharing without addressing those issues. Rather than pushing for a subscription that may not be necessary, perhaps explore ways to stabilize their current setup? MSPs often get a bad rap for pushing complexity.
It sounds like you might be dealing with duplicate SIDs, which has become a known issue recently. It's something that can cause these kinds of authentication errors. Check out this support link for more info: [Microsoft Support](https://support.microsoft.com/en-us/topic/kerberos-and-ntlm-authentication-failures-due-to-duplicate-sids-76f7394d-c460-4882-9ed1-d27e0960f949). Maintaining good practices with system preparation can prevent this kind of issue in the future!
I agree entirely, keeping up with proper procedures can make all the difference here.
I deal with several X-ray and blood scanners too, and honestly, they just don’t adapt well to changes. For one of my X-ray PCs, it needs to stay on Windows 10 with updates disabled to avoid licensing issues - I can't shell out $2.5k for a new license! If you’re looking for a way to enable anonymous/local shares, I had some luck with certain PowerShell commands. I found this helpful link that dives into troubleshooting SMB share issues. Just keep in mind it's not the most secure solution, so if they’re on a service level agreement, a more secure approach might be necessary: [Windows 11 SMB Share Solutions](https://www.rogerirwin.co.nz/windows/Windows-11-24H2-Update-SMB-Share?srsltid=AfmBOorcNUH27-7BINItdEsNCQHmvf8a1xgVLXOBkfR7eYBnVSlXBnzV).
Exactly! This update really seems to bring out the issues that arise from poor practices. If they're not already sysprepping the machines, they definitely need to rethink their approach.