{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/",
        "slug": "trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active",
        "url": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/"
        },
        "title": "Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS",
        "summary": "Use LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "identity-cloud",
            "label": "Identity & cloud",
            "alt": "Governed cloud identity system with connected service and lifecycle nodes.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T17:01:12+00:00",
        "modified_at": "2026-08-27T17:33:24+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 607,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-kerberos-server-not-respond-udp-request-reset-tcp-sessions",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Use this document to connect an official requirement or behavior to observable evidence: Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-kerberos-server-not-respond-udp-request-reset-tcp-sessions\" target=\"_blank\" rel=\"noopener noreferrer\">LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article provides a solution to an issue where Transmission Control Protocol (TCP) sessions created to the server ports 88, 464, 389 and 3268 are reset.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Introduction below H1, Microsoft states: “Sessions using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) on ports 636 and 3269 are also affected.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?</li>\n<li>How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.</p>\n<p>For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>Introduction below H1</strong>; <strong>Introduction below H1</strong> to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.</p>\n<p>Label this evidence set <strong>DSE-20260827-374</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today&#8217;s observation is not a continuing guarantee.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-kerberos-server-not-respond-udp-request-reset-tcp-sessions\" target=\"_blank\" rel=\"noopener noreferrer\">LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to connect an official requirement or behavior to observable evidence: Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides a solution to an issue where Transmission Control Protocol (TCP) sessions created to the server ports 88, 464, 389 and 3268 are reset.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “Sessions using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) on ports 636 and 3269 are also affected.” The research record locates this support at Introduction below H1.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nBuild a reproducible chain from Introduction below H1; Introduction below H1 to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-374 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nLDAP and Kerberos Server not respond to UDP requests or reset TCP sessions — Microsoft",
        "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-kerberos-server-not-respond-udp-request-reset-tcp-sessions) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article provides a solution to an issue where Transmission Control Protocol (TCP) sessions created to the server ports 88, 464, 389 and 3268 are reset.” The research record locates this support at Introduction below H1.\n\n- At Introduction below H1, Microsoft states: “Sessions using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) on ports 636 and 3269 are also affected.” The research record locates this support at Introduction below H1.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\n\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\n\n## Verification and evidence\n\nBuild a reproducible chain from Introduction below H1; Introduction below H1 to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.\n\nLabel this evidence set DSE-20260827-374 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-kerberos-server-not-respond-udp-request-reset-tcp-sessions) — Microsoft"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/",
                "url": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS",
                        "item": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/#article",
                "identifier": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/",
                "url": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/",
                "headline": "Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS",
                "description": "Use LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions to review this narrow operational decision without extending the source…",
                "abstract": "Use LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to connect an official requirement or behavior to observable evidence: Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides a solution to an issue where Transmission Control Protocol (TCP) sessions created to the server ports 88, 464, 389 and 3268 are reset.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “Sessions using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) on ports 636 and 3269 are also affected.” The research record locates this support at Introduction below H1.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nBuild a reproducible chain from Introduction below H1; Introduction below H1 to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-374 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nLDAP and Kerberos Server not respond to UDP requests or reset TCP sessions — Microsoft",
                "datePublished": "2026-08-27T17:01:12+00:00",
                "dateModified": "2026-08-27T17:33:24+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/trace-ldap-and-kerberos-server-not-respond-to-udp-requests-or-reset-tcp-sessions-across-active/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Trace LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions across Active Directory and Windows DNS"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 607,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "LDAP and Kerberos Server not respond to UDP requests or reset TCP sessions",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-kerberos-server-not-respond-udp-request-reset-tcp-sessions"
                }
            }
        ]
    }
}