Am 13.05.2024 um 06:15:24 Uhr schrieb Roman:
> Do you mean 636 instead of 686?
Yes.
> Windows server uses 636 port for sure because when I do "telnet
> home.arpa 686" it's open. But if I use hostname =
> "ldapS://home.arpa:636" - I can't connect with SOGo web page to LDAP,
> no security logs in
Hi,Do you mean 636 instead of 686?Windows server uses 636 port for sure because when I do "telnet home.arpa 686" it's open.But if I use hostname = "ldapS://home.arpa:636" - I can't connect with SOGo web page to LDAP, no security logs in Windows during that operation.But without "S" - hostname =
Am 12.05.2024 um 05:44:53 Uhr schrieb Roman:
> I keep getting these errors:
> " TLS: can't connect: Error in the pull function..
> ldap_err2string
> ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)"
>
> Although if I run the same command without the "S" - ( ldapsearch -H
>
Because of your helpful suggestion, finally using logs on domain controller I was able to fix LDAP authentication with insecure 389 port. According to second paragraph of the official SOGo documentation ( https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#_authentication_using_ldap ) it's
Am 08.05.2024 um 20:56:01 Uhr schrieb Christian Naumer:
> Normally in AD you have to use ldaps, startTLS or Kerberos for Auth
> to the LDAP. In your config I don't see any of that.
I would assume an appropriate error message then that tells about this
- on the LDAP server and on the LDAP client.
Normally in AD you have to use ldaps, startTLS or Kerberos for Auth to the
LDAP. In your config I don't see any of that.
Regards
Christian
Am 7. Mai 2024 16:18:42 MESZ schrieb Marco Moock :
>Am 07.05.2024 um 16:40:58 Uhr schrieb Roman:
>
>> and also, if I run the command from a Linux
Am 07.05.2024 um 16:40:58 Uhr schrieb Roman:
> and also, if I run the command from a Linux machine:
> ldapsearch -H ldap://home.arpa:389 -D "us...@home.arpa" -w
> "Lenovo777" -b "DC=home,DC=arpa".
> then I get a correct response, so it is probably correct.
Can you check the logs at the Windows
If I run the command "dsquery user -name * -limit 0" on a domain controller, I get the following output: PS C:\Users\Administrator\Desktop> dsquery user -name * -limit
Am 07.05.2024 um 12:46:02 Uhr schrieb "Rom@n":
> For test purpose I didn't create anything in domain controller except
> user1 with domain admin privileges and user2 with regular user
> privileges, no OU created, everything is default for Windows Server
> 2016.
I think you should ask at a
Am 07.05.2024 um 09:26:46 Uhr schrieb Roman:
> 1) Deployed a Windows Server 2016 based domain "ldap.local" [...]
This is the first mistake. ".local" is intended for multicast DNS and
DNS resolution will fail if it is not connected to the same link. It
may fallback to unicast DNS then. Use
Hi everyone, Please help to configure authorization with LDAP server based on Windows Server 2016.Recently I have configured SOGo with SQL (Postgres) authentication and it was able to login into SOGo web interface, but I have to migrate to Windows Server 2016 Active Directory and it became a huge
11 matches
Mail list logo
