Hey everyone! I recently migrated my media server from Windows Server 2012 R2 Essentials to a new setup running Windows Server 2022 Standard. The old Essentials version had to be a domain controller, which was quite a hassle. I've now set up my server as a Workgroup, and while my three desktop PCs are connecting to the shared folders without any issues, my Windows 11 laptop keeps failing to connect. Whenever I try to access the shared folders, I get this annoying credential prompt with the message: "The system cannot contact a domain controller to service the authentication request." I've removed all traces of the old domain controller and even switched the laptop to the Workgroup. Oddly enough, I don't see this message on my other devices, and the laptop shows it even when connecting to shares on other Windows clients. When I try to log in with credentials, I encounter an NTLM is disabled error. It's certainly just this one laptop causing trouble. After two frustrating days, I'm considering reimaging the machine from the recovery partition. Does anyone have any ideas on how to stop this laptop from trying to find a non-existent domain controller? Thanks in advance for your help!
3 Answers
Make sure that your laptop has the latest updates, especially if it’s running Windows 11. You might want to specifically check if it’s on version 24H2, as older versions sometimes struggle with network connections. Also, ensure that the local accounts on the laptop have the same passwords as the accounts you use on the server for seamless access.
Sounds like the laptop is still trying to refer back to the old domain settings. Since you've already switched to Workgroup, try uninstalling any old domain-related software like the Essentials Connector if you haven't done that yet. Also, double-check the share permissions; they might not be set correctly for this particular laptop. Sometimes running Windows Updates can also solve strange connectivity issues if it's missing some fixes.
Good point! I had a similar situation, and uninstalling the Essentials Connector made a big difference for me. Definitely check that out.
Since you mentioned the NTLM error, it could also be a security setting issue. Check if NTLM is enabled on the laptop under Local Security Policy. Sometimes, changing the settings to allow NTLM can resolve connectivity problems in a Workgroup scenario, especially if there are permissions set up in a particular way.
Yeah, it’s worth looking into the security policies. I had to adjust that for one of my devices before.
Thanks! I’ll confirm the version and make sure all accounts have matching passwords.