Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Unable to connect to smb shared drive since upgrade to Ventura 13.0

Using macOS Monterey, I could connect to a shared Windows folder.


But now that I've upgraded to MacOS Ventura 13.0, I can't connect to any Windows shared folders anymore.


The OS gets stuck at the authentication page, I'm entering the correct username/password combination, the dialog doesn't accept my input. It stuck here:


I also tried to mount an SMB folder using the mount_smbfs command, but I get an unknown error -1073741811:


I'm sure this issue is with the newer version of macOS, as I experienced the same issue on another PC, everything was working fine just before the update.


Thank you in advance for your help


J-D Gasser


Posted on Nov 3, 2022 6:26 AM

Reply
Question marked as Best reply

Posted on Nov 4, 2022 7:49 AM

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



Similar questions

6 replies
Question marked as Best reply

Nov 4, 2022 7:49 AM in response to JeanDanielGasser

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



Unable to connect to smb shared drive since upgrade to Ventura 13.0

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.