Hello Chris Randall,
Thank you for posting in Q&A forum.
This is a known or by-design issue when Windows Hello or PIN-based logon is used. The PIN is intended only for local authentication and isn’t passed on for network authentication. In other words, the PIN doesn’t work in place of your full password when accessing network resources over a VPN.
Here are a few workarounds you might consider:
- Use your full (domain) password for mapping drives instead of your PIN. Even if you log in with a PIN, network drive mapping (which relies on network credentials) requires the full password. When prompted, enter the password to authenticate the connection.
- Store the correct credentials in Windows Credential Manager. Manually add the network share’s credentials (including the full password) there so that when you map the drive it picks up the right details automatically rather than prompting for a PIN.
- Map the drive manually (or via a startup script) using the full password.
For example, you might run a command like:
net use X: \server\share /user:DOMAIN\username fullpassword /persistent:yes
This step ensures that the network mapping uses the proper network credential rather than the locally scoped PIN.
Here are some similar threads for your references.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best Regards,
Daisy Zhou
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.