The solution is pretty much as Ben describes it. Any server you have running web services can be used to host the proxy.pac file.
You can use Group Policy to configure Internet Explorer to use the shared pac file. This might be helpful: http://www.grape-info.com/doc/win2000srv/internet-gw/wpad/index.html Malcolm -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Tuesday, 27 January, 2009 08:27 To: NT System Admin Issues Subject: Re: Proxy.pac problem On Tue, Jan 27, 2009 at 8:40 AM, Kevan Dickinson <[email protected]> wrote: > I have managed to get our .pac file working when stored locally on the PC. Please share what you did to find and fix the problem, so we can all benefit from your experience. :-) > How do I setup a web server ... IIS (Internet Information Server) comes with Windows and includes a web server; that's prolly your best bet. IIS 6.0 is the version which comes with Windows Server 2003. Getting Started with IIS 6.0 http://technet.microsoft.com/en-us/library/cc775921.aspx > ... and where on the web server should I save the .pac file? Anywhere you want, but you need to create a redirect/alias, such that /wpad.dat on the web server redirects to your proxy.pac file. You also need to configure the MIME Content-Type for .pac files, so IIS identifies the .pac file properly. You also need to configure the "wpad" DNS name. First, the DNS alias. Say your local network uses a default domain of <corp.example.com>. Create a DNS record (A or CNAME) such that <wpad.corp.example.com> resolves to your web server. Second, the web server alias. In IIS Manager, open the root folder for the web site, and create a new virtual directory. Point it at any existing directory (this is temporary). Don't assign any permissions. Once created, open properties on the Virtual Directory, and change it to an HTTP redirect to a URL. Enter a URL which leads to your proxy.pac file on the web server. Third, the content type. Bring up properties on the web site root. Click "HTTP Headers" tab. Click the "File Types" button. Add a new type, extension ".cab", type "application/x-ns-proxy-autoconfig" (don't enter the quotes). > This would seem to be the best way forward now the file is > working when stored locally. Absolutely. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
