• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1227
  • Last Modified:

wpad.dat problem in IIS6 and ISA2000 on win2k3

HI all,

I'm not very clued up about setting up wpad.dat at all but we've just upgraded our proxy server from win2k to win2k3.  Now we're still on ISA 2000 but it looks like we're on new IIS(6).  

Before the upgrade, users used to connect to wpad.dat via automatic configuration script which looked like this. http://server/wpad.dat but now it is http://server:8080/wpad.dat

We need to bypass proxy for a few web sites but we cannot find wpad.dat anywhere on the new server.  If we type http://server:8080/wpad.dat the file comes up and we can save and view it.  But we're not too sure where it's coming from.  We just need to modify this file so we can specify a few websites for bypassing proxy.  I bet you wpad.dat will probably look different as this is IIS6?

Please advise.
0
cooljam23
Asked:
cooljam23
  • 2
1 Solution
 
Chris DentPowerShell DeveloperCommented:

It's autogenerated by ISA Server, it doesn't actually exist as a file on the server as such. You can edit it through the GUI to an extent, whether or not that's appropriate depends on the changes you'd like to make. If the most you need to do is bypass a few servers then you should be able to configure that in IIS without going as far as making your own file.

If you would prefer to use your own then save the contents, edit as appropriate, setup a new website on port 80 and add your wpad.dat file to it (remember that you're either going to have to use DHCP or DNS to advertise your auto-configuration script server).

You will need to add in some extra config for IIS to accept this, open up Internet Information Services Manager, then open the properties for the default website, select HTTP Headers, then click File Types under MIME Map. Add a new type:

Associated extension: dat
Content type (MIME): application/x-ns-proxy-autoconfig

If you want it as a static configuration script then you will need to change the extension to .pac and add another MIME Type for that so IIS will allow it.

HTH

Chris
0
 
cooljam23Author Commented:
Here's what we did -

Went in to ISA management console -> server -> client configuration -> web browser.  Under data access we checked bypass proxy for local servers box and add the web address in there.  Unfortunately this doesn't work.  The users are still going through the proxy for some weird reason.  Any ideas?
0
 
Chris DentPowerShell DeveloperCommented:

We noticed a problem with ours not seeming to keep the files in sync with the configuration we specified - we only just got our proxy servers though, we're a bit new to ISA and such.

Anyway, we've just switched to static wpad.dat and proxy.pac files to try and get the configuration to work as we'd like.

Not really all that much help I'm afraid.

Chris
0
 
NetminderCommented:
Closed, 100 points refunded.
Netminder
Site Admin
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now