Tag Info

Hot answers tagged

9

You should use TCP ports 389 and/or 636. Port 636 is for LDAPS, which is LDAP over SSL. Encryption on port 389 is also possible using the STARTTLS mechanism, but in that case you should explicitly verify that encryption is being done. Microsoft's KB article says: Start TLS extended request LDAPS communication occurs over port TCP 636. LDAPS ...


6

Greg's answer is alright, but your question specifically states that you want to check this from the client, not from the domain controller. So I'll take a crack at it. First way, enable Kerberos logging on your client: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters LogLevel DWORD 0x1 Once Kerberos logging is enabled, ...


3

As long as it LDAP auth only (and not AD/Kerberos etc.), 389 should be sufficient.


3

One way would be to check the domain controller Security event log for Event Id 4264 (logon) events, where the AuthenticationPackageName is NTLM or Kerberos. You should also verify that your domain controllers have auditing enabled, and are capturing the required auditing events. You can create custom Event Viewer filters to make this easier, and filter ...


2

You are mixing up smtpd_sasl and smtp_sasl, the first is for users authenticating on your server to submit emails for delivery, the latter is used when postfix does not deliver directly but also through a relay and postfix itself authenticates. Unfortunately, when connecting to my server with the username and password, I keep getting authentication ...


2

You can limit the scope of Require valid-user by using Limit/LimitExcept : <LimitExcept OPTIONS> Require valid-user </LimitExcept> See apache documentation on Limit


1

Generic solution: I think the Microsoft-centric solution to this is to license using volume keys, and then simply use your KMS server to report on license activation status. Windows 7 and above-solution If volume licensing is not an option, and all of your clients are Windows 7 or newer, you could just query the SoftwareLicensingProduct WMI class on each ...


1

The format for SIP URIs in general is sip:user:password@host:port;uri-parameters?headers So in this case you'd need sip:myuser:mypass@sip.example.com?to=sip:targetuser%40sip.example.com Notice the difference between: sip.example.com:port calls gethostbyname() to resolve DNS sip.example.com without port number uses SRV records instead. You must also ...


1

While I am not proficient in IIS in particular (I deal with Apache mostly), I would expect this is be a custom logging sort of thing. The following page documents some of the advanced logging functionality of IIS; while it doesn't show SSL things in the screenshots, it may still be useful. ...



Only top voted, non community-wiki answers of a minimum length are eligible