Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 14 results
    • Root volume cannot be mounted
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Root_volume_cannot_be_mounted
      Mounting root volume is not possible The root volume is NTFS security style in the EMS log the following errors can be seen: [ 0 ms] Determined UNIX id 0 is UNIX user 'root' [     0] UNIX user 'root' ...Mounting root volume is not possible The root volume is NTFS security style in the EMS log the following errors can be seen: [ 0 ms] Determined UNIX id 0 is UNIX user 'root' [     0] UNIX user 'root' mapped to Windows user 'DEMO\root' [     8] FAILURE: Could not get credentials via S4U2Self based on full Windows user name 'root@DEMO.NETAPP.COM'. Access denied [    10] Could not get credentials for Windows 'root' or SID 'S-1-5-21-57989841-436374069-839522115-2112' Failed to get user credentials.
    • How does LDAP name-mapping work?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_does_LDAP_name_mapping_work
      For user lookups or symmetric name-mapping, LDAP should be specified as a source for passwd and group LDAP is only queried to verify "user1" exists, and if so, the unix account attributes and unix gro...For user lookups or symmetric name-mapping, LDAP should be specified as a source for passwd and group LDAP is only queried to verify "user1" exists, and if so, the unix account attributes and unix group memberships LDAP should not be specified as a source for namemap for this usecase The LDAP client schema in ONTAP specifies which attributes to query to identify a corresponding unix or Windows user account LDAP should be specified as a source for namemap for this usecase
    • CIFS share inaccessible with Secd error: secd.cifsAuth.noNameMap for ONTAP 9
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/CIFS_share_inaccessible_with_Secd_error_secd.cifsAuth.noNameMap_for_Clustered_Data_ONTAP
      4/11/2016 14:07:10 Clus-nas02-02 WARNING secd.cifsAuth.noNameMap: vserver (svm3) CIFS name to UNIX name mapping problem. [     7] Trying to map 'DOMAIN\user1' to UNIX user 'user1' using implicit mappi...4/11/2016 14:07:10 Clus-nas02-02 WARNING secd.cifsAuth.noNameMap: vserver (svm3) CIFS name to UNIX name mapping problem. [     7] Trying to map 'DOMAIN\user1' to UNIX user 'user1' using implicit mapping 9/23/2022 12:33:11 Clus-nas02-02 ERROR secd.cifsAuth.noNameMap: vserver (svm3) CIFS name to UNIX name mapping problem. [    10] Trying to map 'DOMAIN\user1' to UNIX user 'user1' using implicit mapping [    21] Name mapping for Windows user 'DOMAIN\user1' failed with transient errors.
    • secd.nfsAuth.noNameMap reported while mapping unix to windows user
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_map_Unix_to_Windows_user__secd_nfsAuth_noNameMap
      Applies to ONTAP 9 NTFS security style Issue ONTAP is unable to map a Unix user (via NFS) to a Windows user for NTFS permission authorization EMS reports: secd: secd.nfsAuth.noNameMap:error]: vserver ...Applies to ONTAP 9 NTFS security style Issue ONTAP is unable to map a Unix user (via NFS) to a Windows user for NTFS permission authorization EMS reports: secd: secd.nfsAuth.noNameMap:error]: vserver (SVM01) Cannot map UNIX name to CIFS name. Error: Get user credentials procedure failed SECD logs may display: ERR : RESULT_ERROR_SECD_USER_NOT_FOUND ERR : Name mapping for UNIX user 'UID' failed. No mapping found debug: Logged secd.nfsAuth.noNameMap to EMS
    • NFSv4 mount fails when svm root volume security style is NTFS
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFSv4_mount_fails_when_svm_root_volume_security_style_is_NTFS
      Applies to NFSv4 NFSv4 clients return Access Denied and Operation not permitted while mounting volume path Root volume security style is NTFS A sectrace shows the access is being denied on the root vo...Applies to NFSv4 NFSv4 clients return Access Denied and Operation not permitted while mounting volume path Root volume security style is NTFS A sectrace shows the access is being denied on the root volume of vserver: Vserver: svm1 Node Index Filter Details Reason node-02 1 Security Style: NTFS and Access is denied because the NT ACL UNIX user could not be mapped to a valid NT user while reading the user's access rights on an object. Volume: svm1_root
    • Is there any risk for a Windows user to access a volume with Unix security style through name-mapping
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Is_there_any_risk_for_a_Windows_user_to_access_a_volume_with_Unix_security_style_through_name-mapping
      Applies to ONTAP 9 Multiprotocol This question involves the multiprotocol NAS access As long as the multiprotocol is correctly configured and used, there will be no risk How to verify the name-mapping...Applies to ONTAP 9 Multiprotocol This question involves the multiprotocol NAS access As long as the multiprotocol is correctly configured and used, there will be no risk How to verify the name-mapping is working as intended What are the important considerations when setting up CIFS and name-mapping in clustered Data ONTAP Troubleshooting Workflow: CIFS or SMB Access Denied TR-4887: Multiprotocol NAS in NetApp ONTAP Overview and Best Practice TR-4668: Name Services Best Practices Guide
    • Files created from Windows client on a UNIX security volume does not have owner according to the name mapping
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Files_created_from_Windows_client_on_a_UNIX_security_volume_does_not_have_owner_according_to_the_name_mapping
      Applies to Windows user is properly mapped to a UNIX user ONTAP::> vserver name-mapping show -vserver cifs_svm -direction win-unix Vserver: cifs_svm Windows client creates a file on a UNIX security st...Applies to Windows user is properly mapped to a UNIX user ONTAP::> vserver name-mapping show -vserver cifs_svm -direction win-unix Vserver: cifs_svm Windows client creates a file on a UNIX security style volume These files does not have owner according to name mapping rule 1 nfsnobody nfsnobody 0 Oct 28 14:56 win_user_unix_style_after_name_map_new_window.txt 1 nfsnobody nfsnobody 0 Oct 28 14:56 win_user_unix_style_after_name_map.txt 1 nfsnobody nfsnobody 0 Oct 28 14:56 win_user_unix_style.txt
    • CIFS access failure after NS-SWITCH configuration change
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/CIFS_access_failure_after_NS-SWITCH_configuration_change
      Applies to ONTAP 9 SMB/CIFS Issue CIFS access failure after namemap and hosts database change in ns-switch configuration
    • Kerberos authentication for NFS fails when the client uses a client UPN rather than a user UPN
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Kerberos_authentication_for_NFS_fails_when_the_client_uses_a_client_UPN_rather_than_a_user_UPN
      Client system sending a client UPN(host/<client FQDN>@<KERBEROS REALM>) rather than a user UPN [     6] Trying to map SPN 'host/client1.domain@domain' to UNIX user 'host' using implicit mapping **[   ...Client system sending a client UPN(host/<client FQDN>@<KERBEROS REALM>) rather than a user UPN [     6] Trying to map SPN 'host/client1.domain@domain' to UNIX user 'host' using implicit mapping **[     8] FAILURE: Unable to map Kerberos NFS user 'host/client1.domain@domain' to appropriate UNIX user node1 ERROR secd.kerberos.lookupFailed: Unable to map Kerberos user (host/client1.domain@domain) to appropriate UNIX user on Vserver (vs1).
    • Errors in EMS: Unable to make a connection (LDAP (NIS and Name Mapping)
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Errors_in_EMS__Unable_to_make_a_connection_LDAP_NIS_and_Name_Mapping
      Applies to In the EMS log the following errors can be seen: [  8018] FAILURE: Unable to make a connection (LDAP (NIS & Name Mapping):), result: 6942 [  8018] Trying to map 'user1' to Windows user 'use...Applies to In the EMS log the following errors can be seen: [  8018] FAILURE: Unable to make a connection (LDAP (NIS & Name Mapping):), result: 6942 [  8018] Trying to map 'user1' to Windows user 'user1' using implicit mapping [  8122] Hostname found in Name Service Cache [ 10125] TCP connection to ip 10.10.10.5, port 445 via interface 10.20.30.40 failed: Operation timed out. [ 10125] Could not open a socket to 'dc1.demo.netapp.com'
    • Non-root user access returns permission denied
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Non-root_user_access_returns_permission_denied
      Applies to ONTAP 9 CIFS Name-mapping Issue A Linux client accesses the unix security style volume via CIFS protocol Non-root user access returns permission denied