The specified network password is not correct

John Lewter 0 Reputation points
2025-12-11T18:39:51.98+00:00

Trying to map a Azure share on another laptop of mine. On my one laptop I can map it just find in Explorer by simply right clicking on This PC and choosing map network drive. On my other laptop it prompts me for login and once I enter my credentials it keeps saying the specified network password is not correct and I know it is correct. These laptops are basically identical. What could be the issue.

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Marcin Policht 68,300 Reputation points MVP Volunteer Moderator
    2025-12-11T19:29:23.7933333+00:00

    Azure file shares can authenticate in two ways, and your two laptops might be using different ones. When authentication falls back to classic SMB username and password, Windows expects the storage account name as the username and the storage account key as the password. If the second laptop keeps rejecting your credentials, it is often because Windows is silently using a conflicting cached credential from Credential Manager or attempting a different credential set before applying what you type. Removing any saved credentials for the storage endpoint, rebooting, and retrying typically resolves that. SMB 3.0 support and accurate system time also matter, since Azure requires encrypted SMB sessions and rejects requests from devices with clock drift.

    Azure Files can also authenticate with Entra ID. When this is working, you never enter a username or password because Windows obtains a Kerberos ticket tied to your Entra ID or hybrid-joined identity. If one laptop maps the share without issue and the other prompts for credentials, it means the working device is receiving a Kerberos ticket while the failing one is not. That usually happens when the device is not properly Entra ID joined, is signed in with a different identity, cannot reach the required Entra ID endpoints, or does not have the right RBAC permissions. In that case, the system drops to classic SMB authentication, which then fails unless you supply the storage account credentials exactly as Azure expects.

    More at https://dori-uw-1.kuma-moon.com/en-us/azure/storage/files/storage-how-to-use-files-windows?tabs=azure-portal


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    0 comments No comments

  2. Venkatesan S 1,090 Reputation points Microsoft External Staff Moderator
    2025-12-12T04:46:34+00:00

    Hi John Lewter,

    Thanks for posting question in Microsoft Q&A forum,

    It sounds like you're encountering a frustrating issue with mapping your Azure share on your second laptop. Here are a few things you can try to troubleshoot this problem:

    1. Check the Credentials: Even though you mentioned that the credentials are correct, double-check that you're using the exact username and password. If your password contains special characters, make sure to wrap it in quotation marks when entering it in the net use command.
    2. Verify Group Policies: Sometimes group policies can prevent access. You might want to check with your IT admin if there are any group policies that could affect your ability to connect. You can also access the Local Group Policy Editor by running gpedit.msc.
    3. LAN Manager Authentication Level: Misconfigured LAN Manager authentication levels can also lead to issues. You can check and modify this by navigating to the Local Security Policy:
      • Open the Local Security Policy (secpol.msc).
      • Go to Local Policies > Security Options and find Network Security: LAN Manager authentication level.
      • Set it to Send NTLMv2 response only. Refuse LM & NTLM.
    4. IP Address/Host Name Resolution: Make sure you are using the correct syntax to connect. Instead of the IP address, try connecting using the device name in the net use command.
    5. Account Lockout: If you've had multiple failed attempts to log in, the account could be temporarily locked for 15 minutes. If this might be the case, wait and try again.
    6. Event Viewer: If you're still experiencing issues, review the Windows security event logs for any authentication failure errors that might provide more insight into what’s going wrong.

    Let me know how it goes! If you're still having trouble, you might want to explore these follow-up questions to help narrow down the issue:

    • Are you connecting over the same network on both laptops?
    • Was the problematic laptop previously able to connect to the Azure share, or is this a new setup?
    • Are there any specific error codes/messages you're seeing besides the incorrect network password?
    • Have you checked if the credentials ever worked using the cmd command net use to connect to the share on the problematic laptop?

    Hope this helps! If you need more assistance, feel free to reach out.

    References

    Please do not forget to 210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.