After a few hours of investigation, I found how to make access to shared folders work on my Windows Server 2012 R2 form a macOS ventura 13.0 machine
The key to the solution lies in the SMB configuration on the Windows server.
To obtain the configuration, you must:
- Start a PowerShell window with administrator rights
- Enter the command Get-SmbServerConfiguration
Here is the working SMB configuration:
AnnounceServer : False
AsynchronousCredits : 64
AuditSmb1Access : False
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 0
AnnounceComment :
EnableDownlevelTimewarp : False
EnableLeasing : True
EnableMultiChannel : True
EnableStrictNameChecking : True
AutoDisconnectTimeout : 0
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing : False
EnableForcedLogoff : True
EnableOplocks : False
EnableSecuritySignature : True
ServerHidden : True
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RequireSecuritySignature : True
EnableSMB1Protocol : False
EnableSMB2Protocol : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True
EncryptData : False
RejectUnencryptedAccess : True
The blocking parameter in my configuration was "EnableLeasing", it must be set to "True"
Here is the command to make this change on the Windows server:
Set-SmbServerConfiguration -EnableLeasing 1