We have the opposite problem. Our Mac Sonoma 14.1 users cannot establish an SMB connection to the institutional SAN, as the institution's SANM does not support higher than SMB 3.0. We assume Sonoma is trying SMB 3.1.1.
Our Windows 11 users had the same problem, but there's a Window Registry that allows you to set the maximum negotiated SMB version — in this case from SMB 3.1.1 to SMB 3.0. And with that Registry entry, the Windows 11 SMB clients have no problem connecting to the institution's NAS.
Unfortunately, there is no corresponding MaxNegotiatedSMB setting in MacOS' /etc/nsmb.conf file.
Furthermore, there appears to be no way in MacOS Sonama's /etc/nsmb.conf file to limit SMB version to SMB v2.
In other *nix implementations, protocol_vers_map= can have arguments of 1, 2, & 3, corresponding to SMB 1, SMB 2, SMB 1/2.
But the MacOS 14.1 man pages for the nsmb.conf entry protocol_vers_map=, list only 4, 5, & 6, corresponding to SMB 3, SMB 2/3, & SMB 1/2/3 as valid arguments. And this seems to be deliberate, because any of:
protocol_vers_map=1
protocol_vers_map=2
protocol_vers_map=3
seem to have no effect if entered into MacOS 14.1's /etc/nsmb.conf file.