NTL proxies causing problems with Google

BackToMine · 29-03-2005, 18:16

We're sorry...

... but we can't process your request right now. A computer virus or spyware application is sending us automated requests, and it appears that your computer or network has been infected.

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

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

__________________

That error message is from Google after doing a search.

NTL's proxies make Google's servers think all searches are coming from one IP address.

More info: http://www.webmasterworld.com/forum30/28417.htm

From that page, Google employee replies:

Quote:

Hi ogletree! That page originally started because when someone has a virus or a trojaned machine, they often don't realize that their machine may be sending queries to Google without them asking.

Recently, we've started to improve the software, and it can also detect lots of things like rank checking and other automatic queries to Google. Of course, we don't show the message to everybody that comes onto our radar, but our new software looks pretty good at detecting programmatic queries. If you're using WebPosition or other software that sends queries to Google from a program, I'm not surprised if you're going over a threshold where your queries are on the radar.

If you do see this message, I would recommend not sending so many queries to Google--the volume or type of queries are unusual enough that it's attracting greater scrutiny from us. If you avoid sending queries to Google from a program, you'll be as right as rain.

Best wishes,
GoogleGuy

Chrysalis · 30-03-2005, 00:35

hmm I never seen this before but if google start blocking NTL proxies a lot of people will be affected.

IanUK · 30-03-2005, 08:43

I've seen this once before, but to be honest I just thought it was a technical error at Google's end as it disappeared with the next query I made.

bywater · 30-03-2005, 22:58

Been getting the same it only when I use another proxies on the NTL as mine is Coventry and as gone bad again most websites can not be contacted and slow through default one been like it since new upgrade. I shouldn't have to use another proxie but there you go.

BackToMine · 01-04-2005, 19:13

Quote:

Originally Posted by bywater

Been getting the same it only when I use another proxies on the NTL as mine is Coventry and as gone bad again most websites can not be contacted and slow through default one been like it since new upgrade. I shouldn't have to use another proxie but there you go.

Yea I get that same error message.

Google put it a limit on how many searches each IP can make because some SEO consultants have scripts that do hundreds of searches per minute and that affects their servers.

So it must be the more people using Google through one proxy, the more this error popups up.
__________________

Another reason why using transparent proxies is a stupid stupid stupid idea.

Reminds me of AOL junk.

**Paul M** · 01-04-2005, 19:26

Quote:

Originally Posted by BackToMine

Another reason why using transparent proxies is a stupid stupid stupid idea.

No - it just highlights the stupidity of Googles programmers

. ntl's proxy servers pass on the client's real address - and it's very easy to extract this for ip processing (like we do

).

Toto · 01-04-2005, 19:40

Quote:

Originally Posted by Paul M

No - it just highlights the stupidity of Googles programmers

. ntl's proxy servers pass on the client's real address - and it's very easy to extract this for ip processing (like we do

).

Well said that man

__________________

Quote:

Originally Posted by BackToMine

Yea I get that same error message.
Another reason why using transparent proxies is a stupid stupid stupid idea.

Reminds me of AOL junk.

Stupid idea?

Perhaps you can pay ntl's upstream costs then

Google realise that ntl (and other ISP's) use transparent proxies, and the ironic thing is they list sites that can easily detect the proxy and give the correct client IP address.

Chrysalis · 02-04-2005, 03:02

Quote:

Originally Posted by Toto

Stupid idea?

Perhaps you can pay ntl's upstream costs then

Google realise that ntl (and other ISP's) use transparent proxies, and the ironic thing is they list sites that can easily detect the proxy and give the correct client IP address.

Am I right NTL are the only isp in UK now that use compulsary transperent proxies? external bandwidth costs are much lower now days

Toto · 02-04-2005, 08:24

Quote:

Originally Posted by Chrysalis

Am I right NTL are the only isp in UK now that use compulsary transperent proxies? external bandwidth costs are much lower now days

Don't know, but I'd be surprised if ntl were the only ones, particularly broadband enabled ISP's.

IanUK · 02-04-2005, 09:25

The cable ISP's and AOL are the only ones I'm aware of that use Proxies currently, Freeserve/Wanadoo used to, but got rid of them.

I would have no problem at all with ISP's using proxies to save money if they worked properly, but they don't.

cheers

Ian

Toto · 02-04-2005, 09:48

Quote:

Originally Posted by IanUK

I would have no problem at all with ISP's using proxies to save money if they worked properly, but they don't.

cheers

Ian

Fair point, although that could not be applied to all ntl proxies at the moment, although there is no ignoring of the fact that comments made here suggest that certain proxies seem to suffer problems more than others.