Getting "System 67 error: network name not found" while creating FSLogix profile for AVD on Azure Stack HCI.

Aishwarya Upadhye 61 Reputation points
2024-02-12T11:09:19.51+00:00

While following the link https://video2.skills-academy.com/en-us/azure/virtual-desktop/fslogix-profile-container-configure-azure-files-active-directory?tabs=adds to create FSLogix Profile on Azure File Share for AVD on Azure Stack HCI, I encountered a System 67 error while doing NTFS permission: net use y: \\fsprofile.file.core.windows.net\share HDZQRoFP2BBmoYQ(truncated)== /user:Azure\fsprofile Here's the screenshot to the error message: User's image I tried the workaround from the link below but it didn't work for me: https://video2.skills-academy.com/en-us/troubleshoot/azure/azure-storage/files-troubleshoot-smb-connectivity?tabs=windows Allowed the the TCP connection as well. Here are the screenshots to the error message: Screenshot 2024-02-12 144740 Screenshot 2024-02-12 145030

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
300 questions
Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,213 questions
Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,429 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Prrudram-MSFT 22,941 Reputation points
    2024-02-13T04:26:04.4766667+00:00

    Hi @Aishwarya Upadhye

    Looks like there is an issue with the NTFS permission while trying to create FSLogix Profile on Azure File Share for AVD on Azure Stack HCI. The error message "System error 67 has occurred. The network name cannot be found" usually occurs when the network path is not found, or the network name is incorrect.

    To troubleshoot this issue, you can try the following steps: Verify that the network path is correct, and that Azure File Share exists. You can do this by navigating to the Azure portal and checking the storage account and file share.

    Ensure that the correct credentials are being used to access the Azure File Share. You can try using the storage account name and key to authenticate the connection.

    Check if the SMB protocol version, authentication, and encryption settings are configured properly. You can refer to the following link for more information on SMB security settings: https://docs.microsoft.com/en-us/azure/storage/files/storage-files-smb-security.

    Ensure that the firewall settings are configured properly to allow traffic to and from the Azure File Share. You can refer to the following link for more information on firewall settings: https://docs.microsoft.com/en-us/azure/storage/files/storage-files-networking-overview.

    If the issue persists, you can try reaching out to Microsoft support for further assistance.

    --please don't forget to "[Accept the answer]" if the reply is helpful--

    0 comments