Windows 7 32bit + IE11 + Proxy = No Google

stm-tech · June 4, 2014

Hi

We have an issue that has just started to appear since the return from half term break.

Our Windows 7 32bit clients with Explorer 11 can not open Google at all in IE.

It opens just fine in Firefox.

It opens just fine on the x64 bit clients.

No Policy changes have been made to the clients or PC's for IE.

However, if I type the IP address of Google into the IE address bar, it opens.

It is NOT a DNS issue as firefox resolves it just fine.

I have run a RESET of IE

I have checked that the ISA is not blocking anything.

Does anybody have any ideas why IE is starting to misbehave like this?

I have done all available security updates on the PC.

Paul

CraigM · June 4, 2014

Could be something to do with IE11 possibly loading the site over a SPDY connection, that "new" protocol Google are working on to improve on HTTP. See Angry Technician's blog post about the issue here Google not loading first time in IE11 via a web proxy on Windows 8.1? Turn off SPDY support. | The Angry Technician

Michael · June 4, 2014

Will Google open in Compatibility View?

stm-tech · June 4, 2014

No - tried that, also tried all of the other suggestions such as SPDY3 disabled via GPO.

casey · June 4, 2014

We have the same OS and setup as you and have recently moved to IE11 from IE10 without any problems, and Google is our homepage.

Do you get an unable to connect message or just a blank page?

If it's a blank page have you tried to scroll down to see if the page has loaded with a blank space at the top?

stm-tech · June 4, 2014

It is not loading at all. if we type the url into the address bar it simply will not load in IE.

The tab title simply changes to "New Tab" with nothing on the page at all. But if I type the IP address in the address bar, it works fine.

But it is working fine in Firefox on the exact same machine.

stm-tech · June 5, 2014

Ok, I decided enough was enough. I uninstalled IE11, machines then all went back to IE 10 and the problem with Google has been fixed.

This is obviously yet another screw up from Microsoft.

Thanks.

Recommended Posts