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

Vscan servers showing as 'disconnected' along with 'Nblade.noSmbVerNegotiated' in EMS

  1. Last updated
  2. Save as PDF
Views:
569
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

​ ​

Applies to

  • Clustered Data ONTAP
  • ONTAP 9
  • Vscan

Issue

  • After initial setup of a virus scan solution with ONTAP, vscan servers are showing as 'disconnected'

NETAPP::> vscan connection-status show-all -instance
  (vserver vscan connection-status show-all)

                               Node: NETAPP01
                            Vserver: SVM1
                             Server: 10.203.64.62
                      Server Status: disconnected
                        Server Type: primary
                    Vscanner Vendor: -
                   Vscanner Version: -
           Server Disconnect Reason: -
Time When Vscanner Was Disconnected: -
Privileged User Used for Connection: -
   Time When Vscanner Was Connected: -
    Vserver LIF Used for Connection: -

 

  • EMS logs show the following:


[NETAPP01: kernel: Nblade.noSmbVerNegotiated:error]: For Vserver "SVM01", Data ONTAP(R) could not negotiate with the client "10.203.64.62" because it does not support any of the SMB protocol versions that the client sent in the list "".

 

 

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