To be honest, I'm not sure if I have the correct category. Just to give some details:
FW policy: 1. is to pass first our appliance proxy(Blue Coat)
2. will act as backup connection in case the proxy fails
Both policies are set correctly on the firewall but for some reason it is not passing to our proxy and directly passing to our backup route. So it came to my conclusion that there might be an issue with the wpad.dat
Question is is wpad a part of Windows Server? If yes, then I'm on the right forum! haha and I might need help to fix wpad, If not please advise me and will close this thread.
WPAD is actually part of a documented RFC standard which you can find here (WPAD is under 6.4):
http://www.faqs.org/rfcs/rfc3040.html. As such, it's not so much a part of Windows Server as much as Windows Server - like other operating systems, supports its implementation.
The important point to note is that it's not the WPAD discovery process that specifies the actual proxy used. WPAD allows the clients to discover the automatic configuration script URL, not the actual proxy. The PAC script in the
URL is what actually dictates which proxy server is used.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.