Access share on non-domain Windows 10 PC using domain user

Jeremiah Mercier 121 Reputation points

I've spent several hours reading questions & answers for a variety of related problems, but I couldn't find one that matched my configuration, which doesn't seem that complicated:

I'm a remote worker and I have two Windows 10 laptops. Both laptops are connected wirelessly to the same router at home. I log into my personal laptop with a Microsoft account. I log into my work laptop with my company email address. I can also log in to the same account using DOMAIN\USERNAME. Windows Settings shows my work laptop is connected to my company's Azure AD, but it is not joined to the domain. (It is a member of WORKGROUP.) Local Users and Groups does not show my user account, but it is listed as a member of the local Administrators group as DOMAIN\USERNAME. I am able to VPN to my company network as needed, but most of the time I do not use the VPN.

How do I access network shares on my work laptop from my personal laptop? When I try to connect using \COMPUTERNAME I am prompted for credentials. No matter what I use, I get the error "The user name or password is incorrect." I've tried all of the following:

username@keyman .com


MicrosoftAccount\username@keyman .com


I've verified that I can log on locally to my work laptop with username@keyman .com or DOMAIN\USERNAME, so I know I have the correct credentials and password.

I'm wondering if the problem has something to do with trying to log on with a domain account when I can't reach a company domain controller. Of course, both laptops could reach Azure AD. Do they use Azure AD when connecting to a network share?

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,079 questions
{count} vote

1 answer

Sort by: Most helpful
  1. Marilee Turscak-MSFT 35,461 Reputation points Microsoft Employee

    Make sure that there is no duplicate account with a separate Object ID (as this can happen if there is more than one account created with the same UPN but different object IDs). Make sure also that the account exists both on premises and in Azure like Sam said.

    It's possible also that the account got locked out, in which case you can set a lockout policy to prevent this from happening.