This topic describes how to troubleshoot Server Message Block (SMB) mount failures.

System error 53

  • Description

    The network path is not found.

  • Cause
    • The network connection fails.
    • The TCP/IP NetBIOS Helper service is stopped.
    • LanmanWorkstation is not set in the registry.
  • Solution

    Perform the following steps to troubleshoot the error:

    1. Run the following ping command to check whether the IP address of a mount target is accessible and whether the latency is within the expected range:

      ping <The IP address of a mount target>

      • If you can ping the IP address of the mount target, go to step 2.
      • Otherwise, perform the following steps:
        • Make sure that the mount command is valid. For example, the command does not include redundant forward slashes (/), backslashes (\), spaces, or myshare.
          The following example shows a valid syntax of a mount command:
          net use <The target drive letter> \\<The domain name of a mount target>\myshare
          The following example shows a mount command:
          net use z: \\xxxx.cn-hangzhou.nas.aliyuncs.com\myshare 
        • Make sure that the protocol type of the file system is SMB.
        • Make sure that the domain name of the mount target is valid.
        • Make sure that the Elastic Compute Service (ECS) instance and the mount target reside in the same virtual private cloud (VPC).
        • If the ECS instance and the mount target do not reside in the same VPC, make sure that the VPC or virtual private network (VPN) configurations of the ECS instance are valid.
    2. Run the following telnet command to check whether the SMB protocol is enabled:

      telnet <The domain name of the mount target> 445

    3. Check whether the TCP/IP NetBIOS Helper service is started. For more information, see Mount an SMB file system on Windows.
    4. Check the Windows registry.
      Open the Registry Editor, choose HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > NetworkProvider > Order. In the dialog box that appears, check whether the ProviderOrder key contains the LanmanWorkstation value. If not, add the value to the ProviderOrder key.Check the Windows registry

System error 58

  • Description

    The specified server cannot perform the requested operation.

  • Cause

    The Windows operating system that the ECS instance runs is incompatible with the SMB protocol that is used by the file system.

  • Solution

    Make sure that the ECS instance runs Windows Server 2008 R2 or later (excluding Windows Server 2008).

System error 64

  • Description

    The specified network name is no longer available.

  • Cause
    • The IP address of the ECS instance is excluded from the permission groups of the Apsara File Storage NAS file system.
    • The internal IP address or VPC IP address of the ECS instance is incorrectly configured in NAS permission groups.
    • Your payment for Alibaba Cloud services is overdue.
    • The ECS instance and the NAS file system reside in the classic network but belong to different Alibaba Cloud accounts.
    • The protocol type of the file system is not SMB.
  • Solution
    This error occurs when the NAS file system is not accessible. Perform the following steps to troubleshoot the error:
    1. Make sure that the internal IP address or VPC IP address of the ECS instance is included in the permission groups of the NAS file system.
    2. Make sure that the Alibaba Cloud account has a sufficient balance.
    3. Make sure that the ECS instance and the NAS file system are created by the same Alibaba Cloud account if they reside in the classic network.
    4. Make sure that the protocol type of the file system is SMB.System error 64

System error 67

  • Description

    The network name cannot be found.

  • Cause

    Key network services are disabled.

  • Solution
    Enable the following services. For more information, see Mount an SMB file system on Windows.
    1. The Workstation service.
    2. The TCP/IP NetBIOS Helper service.

System error 85

  • Description

    The local device name is already in use.

  • Cause

    The target drive letter is already in use.

  • Solution

    Change the target drive letter and remount the file system.

System error 1231

  • Description

    The network location is unavailable.

  • Cause
    • The Client for Microsoft Networks component is not installed or enabled.
    • The File and Printer Sharing for Microsoft Networks component is not installed or enabled.
  • Solution

    Install and enable the Client for Microsoft Networks or File and Printer Sharing for Microsoft Networks component.

    If the Client for Microsoft Networks or File and Printer Sharing for Microsoft Networks component is installed but not enabled, select the related options.

    System error 1231

    Perform the following steps to install and enable the component:

    1. On the Network and Sharing Center page, click the active network connection.
    2. Click Properties.
    3. In the WLAN Properties dialog box, click Install.
      • Install the Client for Microsoft Networks component.
        1. In the Select Network Feature Type dialog box, select Client, and click Add.
        2. Select Client for Microsoft Networks and click OK.
      • Install the File and Printer Sharing for Microsoft Networks component.
        1. In the Select Network Feature Type dialog box, select Service, and click Add.
        2. Choose Microsoft > File and Printer Sharing for Microsoft and click OK.

System error 1272

  • Description

    Error message: You cannot access this shared folder because your organization's security policies block unauthenticated guest access. These policies protect your PC from unsafe or malicious devices on the network.

  • Cause

    The security policies of the Windows operating system do not allow guest users to access the SMB file system.

  • Solution
    If the ECS instance runs a Windows operating system later than Windows Server 2016 (excluding Windows Server 2016), modify the following registry to allow access from guest users:
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
    "AllowInsecureGuestAuth"=dword:1
    For more information, visit Guest access in SMB2 disabled by default in Windows.