See KB89350 -- MWG requires SMBv1 to be active on your ADFS or Domain Controller.
This is a ridiculous requirement, especially in light of Microsoft encouraging everyone to turn off the legacy protocol. Hopefully the MWG team is working to support SMBv2 or later.
1 of 1 people found this helpful
The McAfee Web Gateway NTLM integration does currently require SMBv1 to be enabled on the domain controllers used for authentication. McAfee is actively working on an integration using SMBv2 but that will take at least several months. In the interim there are many secure authentication options for our customers that would enable them to disable rather than patch SMBv1 on many or all DCs.
- Stand up or use patched domain controllers that still run SMBv1 for MWG to use (could be firewalled instead of patched so only allows SMB connections from other DCs and MWGs).
- Use the NTLM agent (does not need SMB)
- Use Kerberos with user group lookups via LDAP (does not need SMB)
- Use MCP for redirection to MWG when on premise (does not need SMB)
The cloud service never interacts directly with AD so it is unaffected by the disabling of SMBv1.
Official McAfee KB article here https://kb.mcafee.com/agent/index?page=content&id=KB89350
Thanks for the response and updates. Could you add the info about Kerberos/LDAP into KB89350 as well?