Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Why do I see the error noSmbVerNegotiated in the log?

Views:
279
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
cifs
Last Updated:

 

Applies to

  • ONTAP 9
  • CIFS / SMB
  • SMB1 disabled on the storage side

Answer

  • SMB1 has been disabled on the storage controller, the Windows client attempts SMB1 only and as it's disabled it fails as expected.
    Error example:
    5/21/2021 02:11:30  CHBARNASA90-N1   ERROR         Nblade.noSmbVerNegotiated: For Vserver "DATA-SVM", Data ONTAP(R) could not negotiate with the client "10.0.0.12" because it does not support any of the SMB protocol versions that the client sent in the list "<NT LM 0.12;>".
  • After the negotiation failure, the client attempts again but this time with SMB1/SMB2/SMB3

Additional Information

This appears to be incorrect client behaviour as it attempts SMB1 only, and does not present all 3 SMB dialects simultaneously, even though the client does support SMB1/SMB2/SMB3

Scan to view the article on your device