Chrome + WPAD + Firewall = Chrome stops working (IE is fine)

[sparkeh]

Ok bit of an odd one this: we have had a spate of Chrome stopping serving webpages, seemingly randomly.

 

We have both Chrome and IE using WPAD to get the proxy settings and the Windows Firewall is turned on.

When Chrome stops working IE works fine. Taking a look at the firewall logs shows that IE is directing web requests to the proxy whilst Chrome starts trying to send web requests directly (not using WPAD). The only way I can find to fix this is to turn the firewall off, turn off 'automatically detect settings' in Internet Options then renable it. If I then turn the firewall on again, Chrome continues to work (until the next incident).

 

At a bit of a loss with this one.

Edited April 7, 2014 by sparkeh

[AMLinington]

Ok bit of an odd one this: we have had a spate of Chrome stopping serving webpages, seemingly randomly.

 

We have both Chrome and IE using WPAD to get the proxy settings and the Windows Firewall is turned on.

When Chrome stops working IE works fine. Taking a look at the firewall logs shows that IE is directing web requests to the proxy whilst Chrome starts trying to send web requests directly (not using WPAD). The only way I can find to fix this is to turn the firewall off, turn off 'automatically detect settings' in Internet Options then renable it. If I then turn the firewall on again, Chrome continues to work (until the next incident).

 

At a bit of a loss with this one.

 

Looks like it's a known bug: https://productforums.google.com/forum/#!topic/chrome/ztFDM_FcmRQ

 

https://code.google.com/p/chromium/issues/detail?id=18575

 

Latest update from 6 days ago:

 

"This isn't fixed. The issue mentioned fixed in #55 was a regression in how DHCP-based WPAD worked on Windows. The focus of this bug is supporting DHCP-based WPAD on non-Windows platforms. Reopening."

Edited April 7, 2014 by AMLinington

[Arthur]

Chrome 31 had a similar WPAD bug...

 

https://code.google.com/p/chromium/issues/detail?id=318730

 

In this particular case, I had to switch to using DNS for WPAD autodiscovery (from DHCP) to get Chrome working again.

 

Google took several weeks to fix the issue and update Chrome that time, so you may be waiting a while for an official fix.

[sparkeh]

Awww heck.

 

Thanks guys.

 

Thing is I have both DHCP and DNS WPAD setup to support both IE and Chrome.

When its working Chrome can resolve the location of wpad.dat and it only fails when the firewall is running. But it does look like its buggy...