<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>LDAPS on Martijn's Notes</title><link>https://vandenboom.online/fr/tags/ldaps/</link><description>Recent content in LDAPS on Martijn's Notes</description><generator>Hugo</generator><language>fr</language><copyright>Copyright © 2016-2026 van den &lt;span class='bold-rotate'&gt;B&lt;/span&gt;oom. All Rights Reserved.</copyright><lastBuildDate>Sun, 18 Jan 2026 20:19:01 +0100</lastBuildDate><atom:link href="https://vandenboom.online/fr/tags/ldaps/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Packet Capturing for LDAPS Analysis</title><link>https://vandenboom.online/fr/posts/windows_packet_capturing/</link><pubDate>Sun, 18 Jan 2026 20:19:01 +0100</pubDate><guid>https://vandenboom.online/fr/posts/windows_packet_capturing/</guid><description><![CDATA[<p>Troubleshooting LDAPS Connectivity: Using Built-in Windows Tools to Audit Firewall Compliance
As organizations move toward more secure infrastructure, migrating from standard LDAP (Port 389) to LDAPS (Port 636) is a critical step. However, this transition often reveals &ldquo;silent&rdquo; failures where a network firewall might allow the initial connection but block the subsequent SSL/TLS handshake.</p>
<p>At Van den Boom Online, we understand that a smooth user experience starts with a robust backend. In this guide, we’ll show you how to perform packet capturing using only built-in Windows tools to verify if your traffic is reaching its destination or being dropped by security appliances.</p>]]></description></item></channel></rss>