I have an annoying issue with a a couple of ISA servers running ISA standard edition 2004 with SP3.. Both are new installations and are using the Single Network Adapter configuration. The issue I get is that when a browser is pointed at http://www.google.co.uk then IE pops up with the message "Internet Explorer cannot open the Internet site http://www.google.co.uk/" Operation aborted.
I've searched all over the place for information and microsoft seem to claim this is a coding problem on the actual site. However, I have another ISA server, also running ISA 2004, but SP1 where this issue does not happen at all.
Anyone have any idea what this can be? I've tried checking the use HTTP 1.1 through proxy connections but this makes no difference via the two newer proxies.
Thanks for the prompt reply. The problem I have is that the ISA server is chained to an upstream squid and due to my organisations security policy I can't allow ISA or any clients to go direct to the Internet without very good reason, I don't think google not working qualifies.
I'm totally baffled by this, the other ISA which runs an earlier SP has no problem. What actually happens is that the www.google.co.uk or www.google.com page loads ok, then the message appears. After clicking ok, it goes to a page cannot be displayed message!
I guess it might be a SP3 issue, I might try rebuilding one of the new ISA boxes and using SP1 to see if the issue happens with an earlier SP.
Posts: 89
Joined: 18.Oct.2001
From: Boise, ID, USA
Status: offline
All of a sudden this morning...we were seeing many (but not all) of our IE7 proxy clients getting the exact same scenario with www.google.com. I looked at the ISA monitoring, and the access to google.com was just fine....it was the data coming from google that for some reason was causing the error. We ended up changing a IE7 setting to a dfault, adn all was well. I'll post another entry when our customer support folks let me know exactly what they did to make google.com work.
Access directly means add the problem sites into the access directly tab in ISA.
Also make sure use HTTP 1.1 is enabled in IE too.
quote:
ORIGINAL: lorenzotaylor
Thanks for the prompt reply. The problem I have is that the ISA server is chained to an upstream squid and due to my organisations security policy I can't allow ISA or any clients to go direct to the Internet without very good reason, I don't think google not working qualifies.
I'm totally baffled by this, the other ISA which runs an earlier SP has no problem. What actually happens is that the www.google.co.uk or www.google.com page loads ok, then the message appears. After clicking ok, it goes to a page cannot be displayed message!
I guess it might be a SP3 issue, I might try rebuilding one of the new ISA boxes and using SP1 to see if the issue happens with an earlier SP.
I've now added the www.google.com and www.google.co.uk to the access directly section and ensures HTTP 1.1 is enabled in IE. I still seem to get the issue though! This can be resolved temporarily by clearing history, cookies etc but the issue returns after a vew visits to google!
UPDATE: Aparently we're now seeing this issue via our othe ISA server which is running SP1, so I guess it's not a service pack issue.
< Message edited by lorenzotaylor -- 6.Apr.2009 4:31:00 AM >
Still getting this but not as frequently. The google sites have been added to the direct rule and http1.1 is enabled via proxy. The issue does appear to occur only occasionally via the ISA Server with the earlier service pack. Must be something between IE and the ISA as Firefox has no problems at all.
At last - found someone with same problems I am having. I also am running single homed web proxys with upstream web chaining (a Trend micro virus filter).
Started getting the "operation aborted" problems from google a couple of weeks ago.
Seems to be due to the new script for predictive results that google has implemented - the default preference as of a couple of weeks ago.
Quick client fix is to ask them to hit the browser back button to get back to google - click google "preferences" - click "Do not provide query suggestions in search box" - Save preferences. Then get the client to clear all caches.
Not what I want to do for 3000+ customers.
Crux of problem appears to be googles predictive query suggestions- the script always pulls content from client1.google.com. This is a problem because our users have authenticated and accessed the site www.google.com.au (a completely different domain). Work around (for me) is to put in a rule to allow google.com, www.google.com, www.google.com.au and client1.google.com through unauthenticated.
Not an ideal situation. I am still looking for a better fix. Any other ideas would be welcomed.
Thanks for the info Picklebeagle. I'm not sure if this an authentication issue, we've allowed anonymous access as we have a Websense filter that authenticates and blocks unauthorised access.
I've also tried adding the clients1.google.com to the direct access, thoug I'm not sure this will work for us anyway as our ISA's are installed to be a web proxy only and fetch from an upstream squid, they have no direct connection to the Internet.
I'm starting to see other people posting to forums with this problem so hopefuly more info will come to light as to why this has suddenely started happening.
Currently we're just telling user to refresh or click back which usually resolves it in one or two attempts.