Skip to content

Commit a0a6cbf

Browse files
committed
changes
1 parent 82b69f7 commit a0a6cbf

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/windows-server/active-directory/domain-join-log-analysis.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -623,9 +623,9 @@ dc2.contoso.local HOST88.contoso.local SMB2 SMB2:R IOCTL (0xb)
623623
624624
#### About NTLM
625625

626-
Even if you don't see any Kerberos traffic, that doesn't necessarily mean the domain join operation must fail. This is because when Kerberos cannot work under some scenarios, NTLM will be tried as the fallback. As long as nothing is preventing NTLM from working properly such as incompatible LMCompatibilityLevel or blocked NTLM authentication in Group Policy, domain join may still complete successfully with NTLM.
626+
Even if you don't see any Kerberos traffic, that doesn't necessarily mean the domain join operation must fail. This is because when Kerberos cannot work under some scenarios, NT LAN Manager (NTLM) is used as the fallback. As long as nothing is preventing NTLM from working properly such as incompatible LMCompatibilityLevel or blocked NTLM authentication in Group Policy, domain join still completes successfully with NTLM.
627627

628-
Below is an example of successful SMB session setup using NTLM authentication.
628+
See the following example of successful SMB session setup using NTLM authentication.
629629

630630
```output
631631
Source Destination Protocol Name Description

0 commit comments

Comments
 (0)