T
Tommy [A]
Guest
Hi,
We are setting up a new transparent web proxy on one of our subnets, and on the other subnets we are using explicit proxy which the clients get the WPAD url trough option 252 in DHCP. On the new subnet with transparent proxy, no WPAD is configured in DNS or DHCP. We would like to use "Automatically detect settings" on all machines, and this shouldn't cause any issues as it would go to direct communication when not finding WPAD on the new subnet.
Now to the problem: Even trough no WPAD is configured to be offered in DNS or DHCP for the new subnet, IE still pulls the WPAD from the other subnet, if the client ever has been on that network, and tries to use the explicit proxy that blocks the traffic from that network.
Why is IE continuing to grab information from a WPAD that isn't offered? Same goes for Skype for business and Outook that uses exchange Online. Non-MS applications like Chrome does not use the WPAD, and acts correctly.
We have verified that the WPAD isn't offered trough FwcTool so configuration should be correct, but we still seen in C:\Windows\ServiceProfiles\LocalService\winhttp that it pulls the PAC.
Any ideas?
Continue reading...
We are setting up a new transparent web proxy on one of our subnets, and on the other subnets we are using explicit proxy which the clients get the WPAD url trough option 252 in DHCP. On the new subnet with transparent proxy, no WPAD is configured in DNS or DHCP. We would like to use "Automatically detect settings" on all machines, and this shouldn't cause any issues as it would go to direct communication when not finding WPAD on the new subnet.
Now to the problem: Even trough no WPAD is configured to be offered in DNS or DHCP for the new subnet, IE still pulls the WPAD from the other subnet, if the client ever has been on that network, and tries to use the explicit proxy that blocks the traffic from that network.
Why is IE continuing to grab information from a WPAD that isn't offered? Same goes for Skype for business and Outook that uses exchange Online. Non-MS applications like Chrome does not use the WPAD, and acts correctly.
We have verified that the WPAD isn't offered trough FwcTool so configuration should be correct, but we still seen in C:\Windows\ServiceProfiles\LocalService\winhttp that it pulls the PAC.
Any ideas?
Continue reading...