[cifs-protocol] [REG:120080321001822] LDAP connections have hard timelimit of one hour?
obaidf at microsoft.com
Thu Aug 6 17:38:44 UTC 2020
I'll help you with this issue and will be in touch as soon as I have an answer.
Escalatiion Engineer | Microsoft
From: Bryan Burgin <bburgin at microsoft.com>
Sent: Monday, August 3, 2020 12:39 PM
To: Stefan Metzmacher <metze at samba.org>
Cc: cifs-protocol at lists.samba.org; support <support at mail.support.microsoft.com>
Subject: [REG:120080321001822] LDAP connections have hard timelimit of one hour?
Thank you for the question. We created SR 120080321001822 To track this issue. An engineer will contact you soon.
From: Stefan Metzmacher <metze at samba.org>
Sent: Monday, August 3, 2020 7:54 AM
To: Interoperability Documentation Help <dochelp at microsoft.com>
Cc: cifs-protocol at lists.samba.org
Subject: [EXTERNAL] LDAP connections have hard timelimit of one hour?
I just debugged a problem where a Windows AD DC send the following message after exactly 1 hour:
LDAPMessage extendedResp(0) (The server has timed out this connection)
protocolOp: extendedResp (24)
resultCode: unavailable (52)
errorMessage: The server has timed out this connection
The connection was used at least every minute and the last success was returned 2 seconds before this.
These are Windows 2019 DCs, is this special to them, or does this happen with any Windows Version?
I can't find anything related in [MS-ADTS]
Can you clarify this?
More information about the cifs-protocol