Skip to main content

This Site will be down for up to 3 hours on December 2, 2023 from 8 PM - 11 PM PST, to deploy an infrastructure update.

NetApp Knowledge Base

Windows SMB client takes long to report that cifs share does not exist

Views:
471
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • Windows SMB client
  • ONTAP 9
  • CIFS
  • Continuous Availability (CA)

Issue

  • Windows client connects to share, but the share does not exist (or does not exist anymore)
  • Message reported: System error 53 has occured. The network path was not found.
  • It takes around 30 seconds before the error message is reported
  • When the Windows client has a(nother) share already connected to the same cifs server, the response is immediate

 

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.
Scan to view the article on your device