Win10/Server 2019 workgroup mapped drive broke because of credentials

Question

Hi all,

I am working on a strange issue that I have not encountered before. I have a user where their core application is stored on a mapped network drive from a file server. They are running Win10 and the file server is Server 2019. There is no domain and the permissions are set to Everyone on the mapped drive. The user has had this mapping for years now and all of a sudden, the mapping broke. When trying to reconnect the mapping it is asking for an admin account that they do know the creds for anymore. I tried to recreate the drive mapping with another location admin account it gives me the error:

We can’t sign you with this credential because your domain isn’t available. Make sure your device is connected to your organization’s network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

There is no domain. Users are registered to Azure AD, but this has never been a problem in the past. When I try to use a different local admin to authenticate it throws the same error. The workaround I used was to map a network location instead with a different account and that worked, but is not the recommended method per the application provider. Is this a credential caching problem, what do I need to do to fix it? Should I disconnect the mapped drive and then try to remap?

Thanks, Brandon

Answer 1

Hi Karlie,

I will try the Lanman reset when I can get on the users machine. A reboot has not solved the problem so far. And yes the way I worked around the issue was by creating a mapped folder instead of a mapped drive. Unfortunately the software company does not recommend this method, they recommend a mapped drive.

Answer 2

I have not had a chance to test since the workaround is working. I will close this.