This page (revision-3) was last changed on 29-Nov-2024 16:16 by -jim

This page was created on 29-Nov-2024 16:16 by unknown

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
3 29-Nov-2024 16:16 4 KB -jim to previous
2 29-Nov-2024 16:16 4 KB -jim to previous | to last
1 29-Nov-2024 16:16 3 KB unknown to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 10 added one line
NT LAN Manager [Authentication Protocol] is defined in [MS-NLMP|https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nlmp/a4f28e01-3df1-4fd1-80b2-df1fbc183f21].
At line 12 added 9 lines
The NT LAN Manager (NTLM) [Authentication Protocol] is used for [authentication] between clients and servers. These extensions provide additional capability for authorization information including group memberships, interactive logon information, and message [integrity], as well as constrained [delegation] and encryption supported by Kerberos principals.
[Kerberos] [authentication] ([MS-KILE|https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-kile/2a32282e-dd48-4ad9-a542-609804b02cc9]) replaces [{$pagename}] as the [preferred authentication protocol|https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nlmp/a211d894-21bc-4b8b-86ba-b83d0c167b00#Appendix_A_1] However, NTLM can be used when the Kerberos Protocol Extensions (KILE) do not work, such as in the following scenarios.
* One of the machines is not [Kerberos]-capable.
* The server is not joined to a [domain|AD DOMAIN].
* The KILE configuration is not set up correctly.
* The implementation chooses to directly use NLMP.
At line 52 added one line
* [#2] - [MS-NLMP|https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nlmp/a4f28e01-3df1-4fd1-80b2-df1fbc183f21|target='_blank'] - based on information obtained 2021-08-16