When a share fails to be mounted, you can use an automatic inspection script or follow a set of systematic manual troubleshooting steps to pinpoint the problem. This topic describes how to troubleshoot share mount failures.
Use the automatic inspection script to troubleshoot an SMB share mount failure
There may be various reasons for failing to mount an SMB share on Windows. The automatic inspection script can diagnose some of these causes. If the failure remains unresolved after using the script, please submit a ticket to contact us.
You can follow these steps to identify the issue using the automatic inspection script:
-
Log on to the Windows Server where the SMB share mount operation failed.
-
Execute the following commands in PowerShell or PowerShell ISE to download and run the automatic inspection script. Follow the suggestions provided by the script.
-
Download the inspection script.
Invoke-WebRequest https://csg-tools.oss-cn-shanghai.aliyuncs.com/tool/windows_client/alicsg_smb_windows_inspection.ps1 -OutFile alicsg_smb_windows_inspection.ps1 -
Run the inspection script.
.\alicsg_smb_windows_inspection.ps1 -MountAddress \\<gateway_ip>\<share_name> -Locale zh-CNWarningIn this command, \\<gateway_ip>\<share_name> is a placeholder. Replace it with the mount target of your SMB share.
-
How can I fix a share mount failure on a cross-zone high-availability gateway?
-
Verify that the virtual IP address is configured correctly. Mounting will fail if you specify a public IP addresses or virtual IP address that conflicts with route table entries.
-
Conduct ping tests to ensure network connectivity to the virtual IP address of the gateway.
-
For a failure in mounting a Windows SMB share, check the configuration of Lanman Workstation and ensure that the Workstation service and TCP/IP NetBIOS Helper service are enabled.
How can I fix a failure in mounting an SMB share on Windows 2019?
Phenomenon
When mapping a network drive (CIFS share) on Windows, the connection fails and an error dialog box appears with the following error message: The mapped network drive could not be created because the following error has occurred: You can't 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.
Solution
-
On the Windows client, press
Win+Rto open the Run dialog box, entergpedit.msc, and then click OK. -
In the left-side navigation pane of the Local Group Policy Editor dialog box, go to Computer Configuration > Administrative Templates > Network > Lanman Workstation.
-
On the Lanman Workstation page, in the Settings section, select Enable insecure guest logons.
-
In the Enable insecure guest logons dialog box, select Enabled, and click Apply.
-
Attempt to mount the SMB share again.
-
If the mount still fails, restart the Windows client to clear the cache and try once more.
Troubleshoot a mount failure caused by a network connectivity issue between the client and the gateway
Problem description
When you mount a Cloud Storage Gateway file share (NFS or SMB) on a client such as an ECS instance, the mount fails, the connection times out, or the gateway mount IP address cannot be accessed.
Troubleshooting steps
-
Check the network connectivity between the client and the gateway mount IP address:
Run the
ping <gateway_mount_IP>command on the client to test connectivity to the gateway mount IP address. If the ping request fails or times out, continue with the following steps. -
Check whether the private IP address of the client belongs to a standard private CIDR block:
Confirm that the private IP address of the client belongs to one of the following standard private CIDR blocks:
-
10.0.0.0/8
-
172.16.0.0/12
-
192.168.0.0/16
If the private IP address of the client does not belong to one of the preceding standard private CIDR blocks, the gateway may be unable to correctly route traffic to the client. In this case, submit a ticket to add the route to the allowlist.
-
-
Check the security group rules of the client's ECS instance:
Check the security group rules of the ECS instance where the client resides, and confirm whether a restrictive outbound rule is blocking requests to the gateway mount IP address. To check this:
-
Log on to the ECS console and go to the security group management page.
-
Review the outbound rules and check whether a Deny rule exists whose destination includes the CIDR block of the gateway mount IP address.
-
-
Verify the result:
After you complete the preceding configuration adjustments, run the
ping <gateway_mount_IP>command again to test network connectivity. If the ping succeeds, try to mount the share again.