Skip to main content
NetApp Knowledge Base

Multiple ANONYMOUS LOGON in CIFS session show after enabling encryption

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

Applies to

  • ONTAP 9
  • CIFS/SMB
  • SMB Encryption

Issue

  • After enabling encryption, cifs session show reports multiple ANONYMOUS LOGON
  • Multiple different session-id are created, but connection-id is the same:

node  vserver  session-id          connection-id windows-user files protocol-version is-session-signed smb-encryption-status
----- -------- ------------------- ----------    ---------------------------   -- ------  ----- ---------
Node1 Vserver1 3151112364572737813 1701772659    AD\John Doe                   12 SMB3_1  false encrypted
Node1 Vserver1 3151112364572738124 1701772659    NT AUTHORITY\ANONYMOUS LOGON  0  SMB3_1  false encrypted
Node1 Vserver1 3151112364572738161 1701772659    NT AUTHORITY\ANONYMOUS LOGON  0  SMB3_1  false encrypted
Node1 Vserver1 3151112364572738165 1701772659    NT AUTHORITY\ANONYMOUS LOGON  0  SMB3_1  false encrypted
Node1 Vserver1 3151112364572740431 1701772659    NT AUTHORITY\ANONYMOUS LOGON  0  SMB3_1  false encrypted

  • Packet trace show multiple Null user authentication:

Client null user.png

 

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.