This topic describes how to resolve the failure to mount an SMB file system on a Windows ECS instance.

System error 53

  • Description

    The network path was not found.

  • Cause

    The network is not connected or the TCP/IP NETBIOS Helper is disabled.

  • Troubleshooting

    Perform the following steps for troubleshooting.

    1. Run the following ping command to check whether you can access the endpoint of a mount target and whether the latency falls within the expected range.

      ping <The endpoint of a mount target>

      • If you can ping the endpoint, go to step 2.
      • Otherwise, perform the following steps:
        • Check whether the mount command is valid. For example, no redundant or missing forward slashes (/), backslashes (\), spaces, or myshare is found in the command.
          The following provides the valid syntax of a mount command.
          net use <The target drive> \\<The endpoint of a mount target>\myshare
          Example:
          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 endpoint of the mount target is valid.
        • Make sure that the ECS instance and the mount target are located in the same VPC.
        • Make sure the network configurations of the client that is connected across a different VPC or by a VPN gateway to the file system are valid.
    2. Run the following telnet command to check whether the SMB file system is available.

      telnet <The endpoint of a mount target> 445

    3. Check whether the TCP/IP NetBIOS Helper service is enabled. For more information, see Mount an SMB file system.

System error 58

  • Description

    The specified server cannot perform the requested operation.

  • Cause

    The SMB protocol version used on the ECS instance is not compatible with the version used by the file system.

  • Troubleshooting

    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 permission groups of the Apsara File Storage NAS file system.
    • Your payment for services provided by Alibaba Cloud account is overdue.
    • The ECS instance and the Apsara File Storage NAS file system are located in the classic network, but they are created by different Alibaba Cloud accounts.
    • The protocol type of the file system is not SMB.
  • Troubleshooting
    This error occurs when you do not have permissions to access Apsara File Storage NAS file system resources. You can troubleshoot the error as follows:
    1. Make sure that the internal IP address or VPC IP address of the ECS instance is specified in a permission group that is bound to the file system.
    2. Confirm that the balance of the Alibaba Cloud account is sufficient.
    3. Make sure that the ECS instance and Apsara File Storage NAS file system are created by the same Alibaba Cloud account if they are located 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.

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

System error 85

  • Description

    The local device name is already in use.

  • Cause

    The target drive letter is already in use.

  • Troubleshooting

    Change the target drive letter and remount the file system.

System error 1272

  • Description

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

  • Cause

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

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