Apr 08 2021 06:56 AM
Hi,
Has anyone seen an issue where IE is configured to autodetect, downloads the wpad file but then still appears to not use the proxy. I have a Windows 10 machine using CrEdge which works with the same file and installing Chrome on the server also works fine. So I don't think it's the file, this also appears to affect WinHTTP so services using that like powershell and MDE are also trying to go direct.
I've confirmed the dns name is resolvable and that the file is present, i've also got a wireshark trace that shows wpad.dat is requested and gets a 200 response with the file I expect.
Apr 08 2021 09:18 AM
Apr 09 2021 05:33 AM
Apr 09 2021 10:27 AM
Apr 12 2021 06:46 AM
@Reza_Ameri been through this, CrEdge works as expected (it doesn't use WinHTTP to perform WPAD decisions). Weirdly it only appears to be an issue on servers that are promoted to DCs (I think, I need to do some more testing before I am sure)
Apr 12 2021 09:19 AM
Dec 08 2021 05:32 AM