Skip to main content
NetApp Knowledge Base

"nfs: server hostname not responding, still trying" connecting to ONTAP 9.6 or later in a network with high packet loss

Last Updated:

Applies to

  • ONTAP 9.6 and later
  • ONTAP Select
  • NFS
  • Network with high packet loss


  • NFS client logs error messages about nfs server being unreachable

nfs: server <hostname> not responding, still trying

  • NFS client needs to be rebooted to recover
  • A packet trace will show
    • A very high retransmission timeout for packets coming from the client to the storage
    • What appear to be DSACK ranges sent by the storage controller LIF


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.