Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/NFSv3_mount_from_clients_hang_and_timeout_due_to_portmapper_blocked_on_firewall
      Applies to ONTAP 9 NFS v3 Issue Fresh attempts to mount NFS export hang and throw below (or similar) error [root@RHEL7 ~] mount.nfs: Connection timed out Existing mounts continue to work until or unle...Applies to ONTAP 9 NFS v3 Issue Fresh attempts to mount NFS export hang and throw below (or similar) error [root@RHEL7 ~] mount.nfs: Connection timed out Existing mounts continue to work until or unless they are unmounted
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Linux_host_cannot_mount_Network_File_System_NFS_filesystems_due_to_internal_firewall_software
      Linux host software firewall can block NFS traffic to the server.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Can_RPC_port_111_portmap_be_disabled_in_ONTAP
      In ONTAP 9.3 and earlier (including Clustered Data ONTAP 8.x), the portmap service (rpcbind) was always accessible on port 111 in network configurations that relied on the built-in ONTAP firewall rath...In ONTAP 9.3 and earlier (including Clustered Data ONTAP 8.x), the portmap service (rpcbind) was always accessible on port 111 in network configurations that relied on the built-in ONTAP firewall rather than a third-party firewall. Starting in ONTAP 9.7, the portmap firewall service is eliminated, and the portmap port is opened automatically for all LIFs that support the NFS service.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Portmap_service_rpcbind_was_always_accessible_on_port_111_in_network_configurations
      Applies to ONTAP 9 NFSv3 RPC portmapper Issue Logical interface is listening on TCP port 111 (the portmapper)