"Randy" == Randy Rue randyrue@gmail.com writes:
Hello All, We've upgraded our AFF-A220 to 9.13.1 as per https://kb.netapp.com/Support_Bulletins/Customer_Bulletins/SU530
and should be all good to go for next Tuesday's closing of the door on NTLMv2 authentication.
However,
scrb::> vserver cifs session show -vserver sdata -fields auth-mechanism,address,windows-user node vserver session-id connection-id address auth-mechanism windows-user
scrb-a sdata 12223613813613660030 4271015427 10.6.154.156 NTLMv2 FHC\rgrasdue
still shows all of our CIFS connections using NTLMv2 to authenticate (one line is shown of hundreds of connections)
Are we ready for next week's update? Will the auth-mechanism change after we patch our DCs? Or will all our CIFS connections break?
I'm in the same boat, we have a 9.5P5 cluster which just shows NTLMv1 and NTLMv2 logins. Can't seem to get it to do kerberos. I suspect it's something on the DC side of things, but our admins there haven't found anything.
My other system, running 9.3P17 (so definitely affected) is only showing kerberos logins, so we should be ok there no matter what.
John