none
WPAD file not used on every Windows 7 client

    Question

  • Hi all

    We have some problems with our new Windows 7 Clients and their proxy auto-detection (wpad)
    We are using only DNS for finding the wpad.dat file, the option in DHCP is not configured.

    So we installed about 20 new Notebooks with Windows 7 64bit. Same Hardware, same OS, same configuration.
    Some of them never had problems with IE or Firefox to connect to the internet using the proxy. Others have sometimes problem and there are some clients how never could connect. These clients download the wpad file but it seems like they dont use it...


    With GPOs we disabled the caching of Auto-Proxy scripts and the option "Make proxy settings per machine (rather than per-user)" is enabled.

    The old Windows XP Clients dont have problems with the proxy.

    Thx for help

    Wednesday, February 29, 2012 8:57 AM

All replies

  •  Hi,

    Firstly, please let us know what system do you configured as your WPAD server? Forefront TMG or a server running IIS? Have you updated it to the latest edition?

    Also, please let us know the edition of Internet Explorer, Internet Explorer 8 or Internet Explorer 9?

    In general, when "automatically detect settings" is selected, IE will query using DHCP. It will then go to DNS to get the WPAD location if DHCP fails. Finally IE will send HTTP request to download the WPAD file. So it is good for you to make a tracer to see what happened.

    Also, please make sure the GPO “Disable caching of Auto-Proxy scripts” is enable and resetting Internet Explorer settings worth a try.

    Meanwhile, here are some topics for your reference.

    About implementing WPAD  

    Enable Automatic Detection and Configuration of Browser Settings

    Automatic Detection (Internet Explorer 9)

    Troubleshooting Automatic Detection

    Hope this helps.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, March 02, 2012 2:10 AM
  • Hi,

    the system we use as our WPAD server is a Windows server 2003 with IIS 6.0
    Internet explorer is IE 9.

    The GPO "Disable caching of Auto-Proxy scripts" is enabled and we already tried to reset the IE settings. It doesnt help

    I think there is no problem with the IIS server or DNS. All XP clients are working well and even all Windows 7 clients get the wpad.dat file. (we see it in the Temporary Internet Files). It seems like some Windows 7 clients dont use the file...

    Thanks

    Friday, March 02, 2012 10:21 AM
  • Hi,

    the system we use as our WPAD server is a Windows server 2003 with IIS 6.0
    Internet explorer is IE 9.

    The GPO "Disable caching of Auto-Proxy scripts" is enabled and we already tried to reset the IE settings. It doesnt help

    I think there is no problem with the IIS server or DNS. All XP clients are working well and even all Windows 7 clients get the wpad.dat file. (we see it in the Temporary Internet Files). It seems like some Windows 7 clients dont use the file...

    Thanks

    We are also facing the same issue without any resolution. Strange that no reply from Microsoft.

    Browser: IE9
    Working fine on all other browsers but not on IE9 and Windows 7. No option to downgrade to IE8 either, thanks to Microsoft.

    Tuesday, July 17, 2012 11:34 AM
  • We are currently facing the same problem, FF works IE9 doesnt, IE 9 actually doesnt even ask for the WPAd
    • Edited by Ghostroom Friday, February 08, 2013 9:39 AM
    Friday, February 08, 2013 9:38 AM
  • Hi,

    We're having similar problems (some IE9 clients not working, some are).  I'll make this as brief as possible, as I'm sure we've all trawled the net looking for a definitive answer:

    - we're using DHCP option 252 to advise browser on URL for wpad.dat (can't use DNS easily due to per site delegation of AD containers).  This is per scope, though I've tried per server with no difference.

    - currently DHCP server running 2K3R2 on same subnet as clients

    - clients, server are on a child domain "child.root.int"

    - clients are Win7 Pro x86/x64 running IE9

    - Setting IE to point to wpad.dat script directly and everything works as expected, wpad.dat is cached in IE temp files.  wpad.dat is coded correctly and accessible via IIS 7.5 website port 80

    - Setting IE to instead auto detect settings leads to the following (derived from Network Monitor):

       - DHCP INFORM message initiated at browser startup

       - DHCP ACK received from DHCP server containing the correct option 252 and URL string

       - DNS lookups fail as no wpad host name defined

       - For non-working clients IE does not appear to download or use wpad.dat via the DHCP supplied URL. No wpad.dat in cache

    Clearing temporary internet files, deleting HKCU/.../wpad, defaultconnectionsettings and savedlegacysettings keys does not help.  Neither does setting wpadoverride = 1

    Some clients that are not working have wpaddecision=0 wpaddecisiontime=1.  Others have wpaddecision=3 wpaddecisiontime=1.  Working clients appear to have wpaddecision=1 wpaddecisiontime=0 (Microsoft - wouldn't it be great to document these now?)

    Anyone any closer to understanding why WPAD has gone awry with IE9 and DHCP?  I've run out of decent ideas except "bug".

    Thanks,

    Andrew


    • Edited by Fencer128 Sunday, June 23, 2013 11:46 AM Typos
    Sunday, June 23, 2013 11:43 AM