VM proxy & Google problem

Blackened · 09-05-2010, 17:36

Hi all,

I always have to use webcache.virginmedia.com to browse as without it, browsing has always been impossible for me. Today however, using the proxy, Google gives me the below error and entering the captcha characters it suggests simply returns a blank page.

[img]Download Failed (1)[/img]

If I disable the proxy, Google works fine but websites clicked from the results and any others elsewhere, time out (as they always do).

Anyone have any ideas? I've done a scan etc and nothing untoward is happening. Can anyone replicate it using the proxy?

Jon T · 09-05-2010, 17:53

Looks like they've blacklisted the address of the VM proxy. You could try contacting google, explaining to them that it's a proxy address, and them registering multiple requests from the proxy's address is normal.

or.....

Work out why you need to go for a proxy for everything.

BenMcr · 09-05-2010, 17:54

It's likely that all requests to Google through the webcache come from the same IP address - so it's Google anti-flooding/spam/virus protection kicking in

Toto · 09-05-2010, 17:56

Quote:

Originally Posted by Blackened

Hi all,

I always have to use webcache.virginmedia.com to browse as without it, browsing has always been impossible for me. Today however, using the proxy, Google gives me the below error and entering the captcha characters it suggests simply returns a blank page.

If I disable the proxy, Google works fine but websites clicked from the results and any others elsewhere, time out (as they always do).

Anyone have any ideas? I've done a scan etc and nothing untoward is happening. Can anyone replicate it using the proxy?

OK, there is possibly a serious underlying problem if you HAVE to use a web cache to browse the web all the time.

I know that's kind of a "DUH" statement to make, but that would really concern me. What kind of network set up have you got?

Blackened · 09-05-2010, 18:03

Thanks all. Some Googling (ironic..) suggests that it's a spam flood reaction from Google. Phew.

Yeah, I have been thinking it's something I need to look at (why I have to use the proxy) but I seldom have time to sort it out. I usually need to access sites and services very quickly to get stuff done and well, the proxy allows that.

I'm using up to date Firefox. PC is hard wired to a Netgear wireless router. IE has the same problems, if not worse. I've had browsing problems with VM ever since I went from STB to CM, and I've been through a few PC's since then and not always using a router.

Andrewcrawford23 · 09-05-2010, 18:11

Quote:

Originally Posted by Blackened

Thanks all. Some Googling (ironic..) suggests that it's a spam flood reaction from Google. Phew.

Yeah, I have been thinking it's something I need to look at (why I have to use the proxy) but I seldom have time to sort it out. I usually need to access sites and services very quickly to get stuff done and well, the proxy allows that.

I'm using up to date Firefox. PC is hard wired to a Netgear wireless router. IE has the same problems, if not worse. I've had browsing problems with VM ever since I went from STB to CM, and I've been through a few PC's since then and not always using a router.

can you runa tracert to some sites liek google, bbc as this sounds liek routing issue as hte proxy will rotuer oyu another way to it without it

Blackened · 09-05-2010, 18:33

Dunno if it makes any difference but these are taking ages to complete.

Quote:

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms XXXX.know.cable.virginmedia.com [XXXX]
2 40 ms 38 ms 9 ms 10.34.248.1
3 17 ms 15 ms 19 ms manc-core-1b-ge-600-691.network.virginmedia.net [86.28.65.161]
4 11 ms 18 ms 41 ms manc-bb-1b-as0-0.network.virginmedia.net [212.43.163.66]
5 21 ms 11 ms 42 ms manc-bb-1a-ae0-0.network.virginmedia.net [62.253.187.177]
6 37 ms 43 ms 15 ms glfd-bb-1b-ae1-0.network.virginmedia.net [213.105.175.146]
7 17 ms 27 ms 17 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
8 46 ms 17 ms 20 ms 212.58.239.249
9 20 ms 36 ms 47 ms 212.58.238.149
10 27 ms 26 ms 18 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Tracing route to google.co.uk [209.85.227.105]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms XXXXknow.cable.virginmedia.com [XXXX]
2 32 ms 11 ms 15 ms 10.34.248.1
3 25 ms 19 ms 9 ms manc-core-1a-ge600-691.network.virginmedia.net [86.28.65.93]
4 27 ms 50 ms 65 ms manc-bb-1a-as0-0.network.virginmedia.net [213.105.175.1]
5 9 ms 40 ms 26 ms manc-bb-1b-ae0-0.network.virginmedia.net [62.253.187.178]
6 17 ms 14 ms 25 ms tele-ic-3-ae0-0.network.virginmedia.net [212.43.163.70]
7 49 ms 14 ms 15 ms 158-14-250-212.static.virginmedia.com [212.250.14.158]
8 17 ms 16 ms 28 ms 209.85.255.175
9 31 ms 51 ms 54 ms 66.249.95.173
10 21 ms 25 ms 26 ms 72.14.236.191
11 34 ms * * 209.85.243.93
12 81 ms 50 ms 53 ms wy-in-f105.1e100.net [209.85.227.105]

Trace complete.

1st tracert to theplanet.com says: Unable to resolve target system name theplanet.com.
2nd works but :

Quote:

tracert theplanet.com

Tracing route to theplanet.com [70.87.6.117]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms XXXX.know.cable.virginmedia.com [XXXX]
2 19 ms 9 ms 31 ms 10.34.248.1
3 10 ms 30 ms 7 ms manc-core1a-ge600-691.network.virginmedia.net [86.28.65.93]
4 10 ms 19 ms 9 ms manc-bb-1a-as0-0.network.virginmedia.net [213.105.175.1]
5 64 ms 19 ms 44 ms popl-bb-1b-as3-0.network.virginmedia.net [62.252.192.158]
6 33 ms 37 ms 27 ms tele-ic-2-as0-0.network.virginmedia.net [62.253.184.6]
7 * * * Request timed out.
8 147 ms 143 ms 154 ms bd.fd.5746.static.theplanet.com[70.87.253.189]
9 135 ms 166 ms 162 ms 1a.ff.5746.static.theplanet.com [70.87.255.26]
10 136 ms 127 ms 147 ms 82.fd.5746.static.theplanet.com [70.87.253.130]
11 146 ms 153 ms 146 ms theplanet.com [70.87.6.117]

Trace complete.

**Paul** · 09-05-2010, 18:39

Sounds like it may be a dns issue, what dns servers are you using ?

Blackened · 09-05-2010, 18:43

The router & NIC are currently set to auto from ISP, Paul. I have noticed improvements with others in the past but prove to be sporadic so have been sticking with VM's.

:Edit:
Actually changing the DNS servers on the router to OpenDNS and then flipping back to the webcache proxy in the browser gets me all up and running again on Google so thanks for the reminder.
It'd be nice one day to have everything VM default and hunky-dory. I often wonder how someone with lesser 'messing with settings' knowledge would cope with a scenario like this.

Andrewcrawford23 · 09-05-2010, 20:03

point 2-5 also seem a bit high so there could be a problem our side did ypu do that with webcache off?

Blackened · 09-05-2010, 20:36

Yeah, webcache off Andrew.
I'm using OpenDNS now and Google is working but I'm still experiencing intermittent website stuttering so I'm not home & dry just yet.

musicbravo · 09-05-2010, 20:45

It maybe worth checking your MTU settings. Have you tried running any TCP optimising software?

Blackened · 09-05-2010, 20:48

Quote:

Originally Posted by musicbravo

It maybe worth checking your MTU settings. Have you tried running any TCP optimising software?

Nope. Used to be a big fan of Dr TCP in the XP days. Since Win7 though I thought we were all good.
rwin?

musicbravo · 09-05-2010, 20:51

I think receive window size can also have some detrimental effect too

---------- Post added at 19:51 ---------- Previous post was at 19:48 ----------

Yeah didnt realise you were on win 7
There is a version of TCP optimiser for win 7 although I always thought Win 7 was meant to optimise itself
http://www.speedguide.net/downloads.php

Blackened · 09-05-2010, 20:54

Yeah, thanks.
See, with the webcache on I (usually) have zero problems. Quite the opposite - everything loads in a flash, so I'm loathed to mess about with Win7's default on that tbh.