Loading...

3DFS Troubleshooting

I cannot log on to the 3DFS server.

  1. Verify that you are using correct AD user credentials.
  2. Verify that the Samba services are enabled and running.
    1. If SMB support is enabled, you will be able to see the nUSESAMBA additional setting added to the 3DFS server.
    2. The following command must list smbd and winbindd processes as running:

      ps ax | grep -e smbd -e winbindd

  3. Verify that the 3DFS server is added to the AD domain and the connection with AD Controller is intact.
    1. If the 3DFS server was added by using the AD Integration Of Linux Client workflow, you will be able to see the nAD_DONE_DO_NOT_REMOVE_MANUALLY additional setting added to the 3DFS server.
    2. Verify that the following commands run successfully:
      1. The command must display the correct domain name in Realm:

        net ads info

      2. The command must display the message Join is OK:

        net ads testjoin

      3. The command must list all domain users. The command might time out in certain conditions, but you can try out.

        wbinfo –u

      4. The command must display the connection to the domain controller as succeeded.

        wbinfo --ping-dc

      5. The command must return the SID for the user Administrator.

        wbinfo --name-to-sid Administrator

I do not see my SMB shares.

  1. Verify that the Samba services are enabled and running.
    1. If SMB support is enabled, you will be able to see the nUSESAMBA additional setting added to the 3DFS server.
    2. The following command must list smbd and winbindd processes as running:

      ps ax | grep -e smbd -e winbindd

  2. Verify that the SMB shares are listed as NFS-Ganesha exports. The following command must display the required exports.

    ganesha_mgr show_exports

  3. Verify that the corresponding Samba shares are created. The following command must list all SMB shares hosted by the Samba server on the specific 3DFS server. It must have a set of shares.

    net conf listshares

  4. Verify that the 3DFS server for a given network share is correct, and that the network shares are hosted by the 3DFS server being accessed.

I cannot access the SMB share.

  1. Verify that the Samba services are enabled and running.
    1. If SMB support is enabled, you will be able to see the nUSESAMBA additional setting added to the 3DFS server.
    2. The following command must list smbd and winbindd processes as running:

      ps ax | grep -e smbd -e winbindd

  2. Verify that the NFS-Ganesha is running and functional. The following command must run without errors and list all NFS exports.

    ganesha_mgr show_exports

  3. Verify that you have the required set of permissions for the logged-in user. The credentials that you use must refer to the AD user for which access is allowed at the first-level directory.
  4. Verify that the local mount point path is accessible to all users (x bit must be set for others).

I cannot access the file in the SMB share directory.

  1. Verify that the Samba services are enabled and running.
    1. If SMB support is enabled, you will be able to see the nUSESAMBA additional setting added to the 3DFS server.
    2. The following command must list smbd and winbindd processes as running:

      ps ax | grep -e smbd -e winbindd

  2. Verify that the NFS-Ganesha is running and functional. The following command must run without errors and list all NFS exports.

    ganesha_mgr show_exports

  3. Verify that you have the required set of permissions for the logged-in user:
    1. Right-click the parent directory of the file, click Properties.
    2. On the Security tab, check if there are other user names or group names in the list of Group or user names other than the following three entries:
      • Everyone
      • root
      • root

      If there are other ACEs, check if any of the ACE allows the user or group of which the credentials are being used to log in before accessing the file.

    3. If the required user names or group names are missing in the list, then there can be two issues:
      1. The source file does not have the required permissions for the user or group.
      2. There are issues with conversion of SIDs from ACLs fetched from the source file or directory. Verify that the following commands run successfully:

        The command must display the correct domain name in Realm:

        net ads info

        The command must display the message Join is OK:

        net ads testjoin

        The command must list all domain users. The command might time out in certain conditions, but you can try out.

        wbinfo –u

        The command must display the connection to the domain controller as succeeded.

        wbinfo --ping-dc

        The command must return the SID for the user Administrator.

        wbinfo --name-to-sid Administrator

Last modified: 2/6/2019 5:19:30 AM