![]() ![]() ![]() NT Status: STATUS_MORE_PROCESSING_REQUIRED (0xc0000016) SMB2 (Server Message Block Protocol version 2) ![]() Transmission Control Protocol, Src Port: 445, Dst Port: 44682, Seq: 222, Ack: 231, Len: 298 the last error msg is "not supported" ?įrame 3: 366 bytes on wire (2928 bits), 366 bytes captured (2928 bits) I mean, it's smb version 2, which has been around for ever. I am assuming this there is some setting on the netapp that is not configured correctly. Looking at a wireshark trace, I see that the client is attempting to negotiate a session using smb v2.0 but the netapp is returning errors, starting with this. Note: Also, check the smb version running on your client and the default client smb version mentioned in the smb.conf file. Once the command is successful, go to /mnt/smb and check if you are able to see shares.įiler> cifs sessions -t You can try this command from Linux host to mount CIFS shares hosted on NetApp /]# mount -t cifs -o username=Administrator,password=,domain=ABC.COM //192.x.x.x/share1 /mnt/smb Note: When this option is enabled, the Filer uses SMB 2.0, provided client also supports SMB 2.0 To verify max SMB versions supported on your 7-mode Data Ontap, simplest way is to run this command:Ĭheck the SMB2.0 support on your ontap version, this option must be enabled: If you want NetApp (as SMB Server) to serve SMB3.0 version to clients, then you must be on cDOT/ONTAP and client must also support the higher version (For them to negotiate). Hence, it is not going to work with Data ontap 7-mode (as SMB server, 7-mode OS version doesn't matter, SMB 3.0 is never introduced in 7-mode and will never be b'cos the code development is stopped, cDOT/ONTAP is the only way forward wrt SMB3.0 support). SMB 3.0 (newer versions)only available in cDot/ONTAP (Precisely cDOT 8.2 and later). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |