Active Directory Authentication is not working

I don't know how it is with Windows Server 2012 but we had to switch from port 389 to 636 in 2020 because Microsoft started enforcing LDAPS (we use Windows Server 2019). These are our settings on the UTM now:

If you use recipient verification in the SMTP proxy you also have to change a config file in the UTM via SSH: www.frankysweb.de/.../

Hi, no server 2012 uses regualr ldap, already tried it in a lab, i'm pretty sure that it's problem related to the antivirus solution at the customer.

Are you aware oft the recent domain join hardening changes introduced by microsoft?

See KB5020276 and note the modified timeline, especially the depreciation of NetJoinLegacyAccountReuse after Aug 10 2023.

I have already recreated the exact sitation in a lab, the newest patches were installed on my machine, it was working witthout a problem

i also just tried to domain join the sophos to the active directoy, it's now saying it was successfully joine to the domain, however the surprising this is that the authentication server is still staying failed to bind to ldap

And the logon type is 4672 in the event viewer for the domain join of the sophos 

Hey Georg Zoeller  refer - Troubleshoot issues when joining the UTM to an Active Directory domain.

Hey Georg Zoeller  - Event ID 4672 – Special Privileges Assigned To New Logon.

Hey Georg Zoeller  - Event ID 4672 – Special Privileges Assigned To New Logon.

I mean i dont quite think it's a problem with adding the sophos to the domain, i mean it now says it's joined to the domain, however the authentication services is still not working

UTM 9 uses aua as the authentication service, enable extended authentication debug output:

1. Access the UTM backend via console or SSH.
2. Login as root.
3. To enable debugging, enter command: killall -USR2 aua.bin
4. To disable it, enter the command again.
   
   
   

When extended debugging is enabled, more information regarding authentication requests will be logged to /var/log/aua.log. Note: this does not include AD SSO authentication requests.

And is the UTM on the latest version 9.716 ? Check the release notes.