Mapping Azure Fileshares - getting "The specified network password is not correct." for 1 sa but not for another

Jane Cassell 0 Reputation points
2024-05-03T15:46:49.93+00:00

here's the layout - 3 subscriptions, each with their own vNet - 1 Core subscription with 2 spokes peered to the core but not to each other - Route Tables in the spokes point to a firewall in Core which passes traffic onwards to the other spoke - no known issues there

However, 1 VM in spoke A needs to connect to 2 file shares - 1 file share on a Files SA in Spoke A & 1 file share on a Files SA in Spoke B

Both SAs are configured the same as far as i can see - they are both configured to use AD DS - user is Contributor on both SAs

the file share from Spoke A maps correctly without asking for credentials

the file share from Spoke B fails to map and asks for credentials - rejecting the password when it is entered with the error "The specified network password is not correct."

i have gone through every setting in the 2 accounts and they look the same

it is the same VM and the same user trying to connect - but 1 works and 1 fails.

Any help would be appreciated

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,769 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,455 questions
{count} votes

3 answers

Sort by: Most helpful
  1. hossein jalilian 4,285 Reputation points
    2024-05-03T21:12:16.1266667+00:00

    Thanks for posting your question in the Microsoft Q&A forum.

    I recommend reviewing the following aspects:

    • Ensure that the Storage Account in Spoke B is not configured to restrict access to specific IP ranges or virtual networks
    • If the network connectivity seems fine, try mapping the file share using the IP address of the Storage Account instead of the DNS name
    • If the issue persists, consider creating a new file share in Spoke B and testing the connection again

    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

    1 person found this answer helpful.

  2. Jing Zhou 2,790 Reputation points Microsoft Vendor
    2024-05-07T06:56:52.3633333+00:00

    Hello,

     

    Thank you for posting in Q&A forum.

    To further check this issue, please kindly follow steps below:

    1.Run below PowerShell command to check if you can resolve the storage account name:

    Test-netconnection -computername <storageaccount>.file.core.windows.net -port 445

    It will help check if you have proper network access to the storagea account.

    2.It can also be caused by the authentication issue, you can refer to below Microsoft Official Documentation for further details.

    https://learn.microsoft.com/en-gb/azure/storage/files/storage-files-identity-auth-domain-services-enable?tabs=azure-portal

    3.Run network monitor or wireshark when reproducing the issue and capture the network trace. In the trace you will get more insights and information.

    Hope this answer can help you well.

     

    Best regards,

    Jill Zhou


  3. Nehruji R 3,041 Reputation points Microsoft Vendor
    2024-05-07T08:18:29.91+00:00

    Hello Jane Cassell,

    Greetings! Welcome to Microsoft Q&A Platform.

    Thank you for providing the detailed layout and issue description! Please check the below following and troubleshoot the issue,

    Hope this answer helps! Please let us know if you have any further queries. I’m happy to assist you further.


    Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments