A User Fails to Access a File Sharing Resource

Symptom 1: When a user attempts to access a file sharing resource, the system displays a message indicating that access fails due to a network connectivity issue.

Symptom 2: When a user attempts to access a file sharing resource, the system displays a message indicating that access fails due to nonexistence of the file or directory on the server.

Symptom 2: When a user attempts to access a file sharing resource, the system displays a message indicating that access fails due to insufficient operation permission.

Cause 1: The file server for the file sharing resource did not exist or the route between the file server and the FW was unreachable.

Cause 2: The host address for the file sharing resource is a domain name, but the DNS server was not configured or configured incorrectly.

Cause 3: Security policies were configured incorrectly.

Cause 4: The directory for the file sharing resource did not exist on the file server or was not shared.

Cause 5: In the File Sharing Login page, the user entered an incorrect user name or password.

Cause 6: The user had no rights to operate the directory for the file sharing resource.

Causes vary depending on symptoms.

• Symptom 1: cause 1, 2, or 3
• Symptom 2: cause 4
• Symptom 3: cause 5 or 6

• Cause 1: The file server for the file sharing resource did not exist or the route between the file server and the FW was unreachable.
  1. Log in to the Web UI for the FW as the system administrator. In the navigation tree, choose Monitor > Diagnosis Center.
  2. Click the Ping icon. In Host Name or IP Address, enter the intranet server IP address.

  3. Click Ping to check the network connectivity.

     If the IP address cannot be pinged, the network between the SSL VPN gateway and the file server is faulty. Verify the connections between the SSL VPN gateway and the file server and route configurations.

• Cause 2: The host address for the file sharing resource is a domain name, but the DNS server was not configured or configured incorrectly.
  1. Log in to the Web UI for the FW as the system administrator. In the navigation tree, choose Network > SSL VPN > Gateway Configuration.

  2. Verify that Primary DNS Server is correctly configured. If Primary DNS Server is configured incorrectly, enter the correct DNS server IP address.

     A correct DNS server meets two conditions:

     • The route between the DNS server and the FW is reachable.
     • The mapping between the IP address and the domain name of the file server is found on the DNS server.

• Cause 3: Security policies were configured incorrectly.
  1. Log in to the Web UI for the FW as the system administrator. In the navigation tree, choose Policy > Security Policy > Security Policy.
  2. In the displayed page, check the security policy configuration. If there is a security policy that disables the user from using the file sharing resource, change this security policy.

• Cause 4: The directory for the file sharing resource did not exist on the file server or was not shared.

  Verify that the directory for the file sharing resource exists on the file server and is shared.

• Cause 5: In the File Sharing Login page, the user entered an incorrect user name or password.

  The user can access SMB-type file sharing resources only after login. Verify that the login user name and password are correct. If the user name or password is lost, contact the file server administrator.

• Cause 6: The user had no rights to operate the directory for the file sharing resource.

  For SMB-type file sharing resources, the user may not have the read permission. Contact the file server administrator to assign the read permission.

  For NFS-type file sharing resources, the user's UID or GID may be incorrect. Contact the file server administrator to assign correct UID and GID.