Smoothwall and Google redirect

[CyberNerd]

When going through the smoothwall filter, Google redirects us to the following page:

 

http://sorry.google.com/sorry/?continue=http://www.google.com/

 

We're sorry...

 

... but your query looks similar to automated requests from a computer virus or spyware application. To protect our users, we can't process your request right now.

 

We'll restore your access as quickly as possible, so try again soon. In the meantime, if you suspect that your computer or network has been infected, you might want to run a virus checker or spyware remover to make sure that your systems are free of viruses and other spurious software.

 

If you're continually receiving this error, you may be able to resolve the problem by deleting your Google cookie and revisiting Google. For browser-specific instructions, please consult your browser's online support center.

 

If your entire network is affected, more information is available in the Google Web Search Help Center.

 

We apologize for the inconvenience, and hope we'll see you again on Google.

To continue searching, please type the characters you see below:

 

It doesn't happen when I use the same connection through a squid proxy, and doesn't appear to be browser related. Any ideas?

[tom_newton]

Would suggest it is a lot of queries coming from the IP of your smoothie box. This may have triggered google's spider-sense.

 

You can tell from your access logs if a) theres anything fishy going on on the SW (header mangling etc) or b) there have been some unfortunate queries from one of your PCs.

 

If you have FP2 and enabled "search term filtering" that also might give some useful reports.

[MPorter]

Dont know if its any use, but we've had this all day, and we don't have smoothwall. Our ISP is EMBC.

 

Maria

[ChrisH]

We get it on the Lancs NGFL ever now and again. It is as said, google saying there have been so much traffic from one IP that it is making sure it isnt some automated badness by asking you to fill in the code.

[nicholab]

We had this problem with our web filter it was something to do with our page redirection to Google. we changed it to point to "about:blank" and it has been fine since.