1 of 1 people found this helpful
Hello guys, how are everyone.. I hope fine.
So, in contact with McAfee Support, I reproduce the problem in my labs and their capture the traffic and show me whats was the problem.
I was using all the time the NTLM Authentication, and, after tests and traffic capture, after the proxy sent the NTLMSSP_CHALLENGE to the browser, google chrome of firefox won't send to the proxy the GET with the "NTLMSSP_AUTH, User". They just jump this request.
How the NTLM auth must occour normally
And how the NTLM Authentication was occour wihout the NTLMSSP_AUTH
I do a test using LDAP authentication, and the problem don't occour. Works fine, even with the Microsoft KB3189866 or KB3193494.
Again, to me, in the McAfee proxy, using the LDAP Authentication, it's work fine... Don't needed uninstall those KBs.
So, what I need to do is use the LDAP Authentication instead NTLM, and wait for Microsoft or the browsers company to fix this problem, because, to machine out of the domain in a large enterprise with remote sites, it's almost impossible to remove the KB and block his installation.
I hope this help someone...
Good night @LL
Thanks to McAfee Support.
Thanks for this information. I stick to NTLM because it's easier but I imagine I'll need to use LDAP as I may end up in the same situation.
Kbolt, good night.
I'm still using NTLM for all the company, it's around 4000 hosts
I have only few machines have this problem, because it's personal notebook with Windows 10 1607, out of domain. So I used LDAP only for these computers using IP Address as "criteria". Of course, to this machines the IP Addres is static.
As workaround, so far all good.... =)