wpad.dat

wpad.dat

am 26.11.2007 19:12:23 von Rob Nicholson

I must be missing something really daft here :-) Existing infrastructure has
a IIS 5 box running on Windows 2000 server. At the root of the IIS website
is the wpad.dat file which is a little JavaScript file used to configure the
proxy server. Our IE clients are configuration to load
http://server01/wpad.dat for their automatic configuration script. Works
fine.

Building new pilot AD domain and checking out same functionality over there.
Same file is sat in root of http://vserver004/wpad.dat but it doesn't work.

If you go to a browser and manually type http://server01/wpad.dat into the
address line, you get the file dialog saying "Find, Save, Cancel" - as
expected. Try it with the new IIS server by typing
http://vserver004/wpad.dat and IE reports "Page not found".

The IIS server is working as I've got a simple http://vserver004/test.htm
document in there and that loads.

Strangely, if I renamed wpad.dat to wpad.txt and try
http://vserver004/wpad.txt, the script displays. So it's resolving okay.
Just that it doesn't seem to like serving up wpad.dat file.

What stupid thing have I missed? Some configuration of extensions, script
access?

Thanks, Rob.

Re: wpad.dat

am 26.11.2007 19:22:36 von Kristofer Gafvert

Hi Rob,

You probably need to add a MIME type for the .dat extension. IIS 6 does not
serve unknown MIME types by default.

"IIS 6.0 does not serve unknown MIME types"
http://support.microsoft.com/kb/326965

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


"Rob Nicholson" skrev i meddelandet
news:e7GRkfFMIHA.3916@TK2MSFTNGP02.phx.gbl...
>I must be missing something really daft here :-) Existing infrastructure
>has a IIS 5 box running on Windows 2000 server. At the root of the IIS
>website is the wpad.dat file which is a little JavaScript file used to
>configure the proxy server. Our IE clients are configuration to load
>http://server01/wpad.dat for their automatic configuration script. Works
>fine.
>
> Building new pilot AD domain and checking out same functionality over
> there. Same file is sat in root of http://vserver004/wpad.dat but it
> doesn't work.
>
> If you go to a browser and manually type http://server01/wpad.dat into the
> address line, you get the file dialog saying "Find, Save, Cancel" - as
> expected. Try it with the new IIS server by typing
> http://vserver004/wpad.dat and IE reports "Page not found".
>
> The IIS server is working as I've got a simple http://vserver004/test.htm
> document in there and that loads.
>
> Strangely, if I renamed wpad.dat to wpad.txt and try
> http://vserver004/wpad.txt, the script displays. So it's resolving okay.
> Just that it doesn't seem to like serving up wpad.dat file.
>
> What stupid thing have I missed? Some configuration of extensions, script
> access?
>
> Thanks, Rob.
>

RE: wpad.dat

am 27.11.2007 10:17:38 von wjzhang

Hi Rob,

As Kristofer stated, if the new site is on Windows Server 2003 IIS 6.0, the
problem is most likely .dat isn't included in IIS6 MIME type list by
default. IIS6 desn't serve unknown file types per its enhanced security
restriction. You should manually add the .dat MIME type:

In IIS mmc, right-click the server(computer icon) to open its properties.
Click the MIME type button, add the .pac and its MIME string as below:

Associated Extension: .dat
Content Type(MIME): application/octet-stream

After this, please restart IIS service by running iisreset command and then
test opening the file in IE again.

If issue persists, please update here.

Have a nice day.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Re: wpad.dat

am 28.11.2007 12:04:16 von Rob Nicholson

> You probably need to add a MIME type for the .dat extension. IIS 6 does
> not serve unknown MIME types by default.

That is probably it! Thanks...

Re: wpad.dat

am 28.11.2007 12:05:03 von Rob Nicholson

> default. IIS6 desn't serve unknown file types per its enhanced security
> restriction. You should manually add the .dat MIME type:

I suspected it was something to do with the enhanced security (most things
are ). I'll have a look next week,

Thanks all, Rob

Re: wpad.dat

am 28.11.2007 13:19:16 von Rob Nicholson

> You probably need to add a MIME type for the .dat extension. IIS 6 does
> not serve unknown MIME types by default.
>
> "IIS 6.0 does not serve unknown MIME types"
> http://support.microsoft.com/kb/326965

Adding .dat as a MIME extension worked a treat. I guessed at
application/octet-stream as the type...

Rob.

Re: wpad.dat

am 29.11.2007 09:07:57 von wjzhang

Rob,

Glad to see you've resolved the problem.

Have a great day.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx .

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.