Skip to main content
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video.
NetApp Knowledge Base

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

Views:
197
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
cifs
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

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support