#If you have older CIFS SVM's please look at this...

1 messages · Page 1 of 1 (latest)

dawn abyss
#

https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/ONTAP_Guidance_for_Microsoft_Security_Update_KB5073381_CVE_2026_20833

Microsoft is enforcing extra Kerberos security, in a hotfix... which most likely will render your clients unable to access the shares on your CIFS SVM by its name. (IP works).
"vserver cifs security show -vserver * -fields advertised-enc-types" Will show if you can run into this issue... (if you only have "rc4,des" you should change it to "aes-256,aes-128")...
Thse values are set at CIFS Machine Creation so if it was awhile ago you will most lokely have the old values set and be at risk...

#

If you have older CIFS SVM's please look at this...

lunar grove
#

yep, i have this going on right now

dawn abyss
#

Before we found the cause, we found out that a NetBIOS alias isn't affected some how... so we created an alias and DNS record and modified all DFS leafs... Why do Microsoft always do this? 😉

tired lily
#

because.. why would they pay testers when they have the whole world using their crap to do it for free

zealous hound
#

What is the impact of changing "rc4,des" setting to "aes-256,aes-128" for current connected clients?