Link to home
Start Free TrialLog in
Avatar of ccsoitd1
ccsoitd1

asked on

Google.com does not load the first time IE11

So i'm having an issue with our new windows 8.1 devices where the first time they browse to http://google.com the page instantly comes up and says "This page can't be displayed" refreshing the page brings it up just fine.

this happens every time i close and re-open the browser but once it does it the first time it loads fine the rest of the time.

we are going through a websense proxy and I'm pretty sure the proxy has something to do with it i just can't put my finger on it.

scenarios
Home page = intranet
open ie, intranet loads fine
browse to google, page doesn't load
refresh page, loads fine

homepage = intranet
open ie, intranet loads fine
browse to yahoo, loads fine
browse to aol, loads fine
browse to google, page doesn't load
brows to yahoo, loads fine
browse to google, loads fine

homepage = msn.com
open ie, loads fine
browse to google, page doesn't load
refresh, page loads fine

homepage = google.com
open ie, page doesn't load
refresh, page loads fine

bypass proxy
same scenarios as above google loads fine every time.

i checked my proxy logs and everything appears to be fine i think i need a little guidance here. also this is not a reported problem from users using windows 7 and IE8 or IE9 and i don't even remember having the issue during the short time i was testing windows 8 and IE10 but at that time i may have had my proxy bypassed. all the issues appear to be with windows 8.1 and IE 11
Avatar of ccsoitd1
ccsoitd1

ASKER

forgot to mention that i do not have the same issue in Chrome or FireFox with the proxy enabled.
SOLUTION
Avatar of Phiwi Moyo
Phiwi Moyo
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
That's funny cause I did do some Google searching before I posted this i'm usually on my last straw when I post here i like to figure stuff out for myself. I guess i just wasn't using the right search terms.

Seems strange that without the proxy it works fine. Is there a setting that I could check/force to see possibly I can get his working or should I just wait for it to resolve itself?

We have to skip IE10 here because it makes a couple of our internal pages show up as Chinese symbols, only IE10 though 8,9, and 11 all load the website properly.
I did a search for the IE11 google issue, those appear to be relating to the rendering of the page which is fine, it's just when i visit for the first time it doesn't load. after that it loads perfectly fine.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Alright well I guess I'll just use the wait and see approach.

thank you for your replies.
We are having the same issue with our Websense and have put in a support ticket. Just curious what version of Websense are you running? We are running 7.7.3 and haven't updated to 7.8.1 yet because of technical requirements. If I get a resolution from Websense I will update this post.

I have also found if you modify the security settings in IE 11 to turn off tls 1.0, 1.1 and 1.2 it works fine with proxy on. This isn't a solution, but just more information.  It has something to do with sites begin https only. We have noticed the same thing with other https only sites google, facebook, gmail, youtube and so on. But it doesn't seem to effect all https sites just the ones that force https all the time.
@fixitben Unticking all the TLS boxes solved the problem for us on Google sites but some sites won't work if you switch off TLS.

e.g. https://www.whirlpool.net.au/
@Toolguy: I don't think do disable TLS is the solution. But to turn off SPDY Support is.
Check out this Post:

http://angrytechnician.wordpress.com/2014/01/16/google-not-loading-first-time-in-ie11-via-a-web-proxy-on-windows-8-1-turn-off-spdy-support/
@InfrontStaff I had almost given up on this. Turning off SPDY support solved the issue and has the advantage of not causing any unwanted side effects.

Thanks for your post.
Hi,
I did not find a reliable working solution for this behavior yet.

Fresh installed Windows Server 2012 R2 as Terminal Server. One of our company sites configured with a direct URL link on desktop.
Launching that link brings the cannot be displayed message instantly.
Refreshing or launching the link again brings the website.
Waiting a minute gets again the cannot be displayed message. Also if the website is left open, the content of a frame which should refresh periodically disappears for the above message again.
This issue never seems to happen with the SharePoint page, which is configured as home page - so it must have to do with some interaction between IE and the targeted website. No https page. Happens also for regular newspaper websites.

Windows Update fails with 8024402F, which indicates that the service cannot be reached. Sometimes immediately, sometimes after delay. Not sure, if this is related. The first updates after installation had no problem, so it might be as well an issue with the updates installed meanwhile.

Name resolution points to the proper IP address (run nslookup, just before the first attempt to open the website).
SPDY in Internet Explorer is disabled.
No proxy involved and also not configured in IE.
netsh int tcp set global ecncapability=disabled has been executed in Admin prompt.
Power save and green features of the network card have been disabled, the Realtek network card driver is the most recent available.
A few reboots have been done. Doesn't play a role, which role the user has - admin or limited user account.

Happens reproducable only on that server ... almost never on a 64 Bit Windows 8.1 client  which I run as a desktop.
If I keep a permanent ping on the website, it seems to load every time successfully, so the handshake to the DNS server could be the issue (which is in charge of the SharePoint site, which every time loads, but needs to forward all other requests).

Best greetings from Germany
Olaf