Can someone help? can't reach a website....

pjcoop · 12-02-2005, 10:48

Hi,
I need a favour.. please...anyone....
I'm trying to reach a website 'www.greytalk.com' it's a forum about Greyhounds (nothing dodgy!!).
I can view the site from work but can't see it from my home NTL BB connection. I think there may be a DNS or routing issue.
I've tried contacting NTL support but.... you guessed it.... blank (via email).
Can anyone else see this site?

Here's a trace route to the domain... (at the bottom of the email)

Why can I see the site from my work but not on NTL BB ?????

Thanks in advance

Paul
---------------
traceroute to www.greytalk.com (64.246.20.91), 30 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 42.031 ms 1.177 ms 1.157 ms (Airport network)
2 10.x.x.x (10.x.x.x) 8.622 ms 8.222 ms 7.584 ms
3 wapk-t2cam1-b-ge-wan42-117.inet.ntl.com (80.xxx.xxx.xxx) 7.849 ms 7.483 ms 13.746 ms
4 popl-t2core-b-ge-wan62.inet.ntl.com (62.255.81.173) 36.49 ms 9.296 ms 17.94 ms
5 pop-bb-b-so-320-0.inet.ntl.com (62.253.185.69) 12.842 ms 8.654 ms 8.417 ms
6 gfd-bb-a-so-500-0.inet.ntl.com (213.105.172.137) 10.253 ms 11.07 ms 8.96 ms
7 gfd-bb-b-ae0-0.inet.ntl.com (213.105.172.6) 9.857 ms 12.341 ms 9.19 ms
8 bre-bb-a-so-000-0.inet.ntl.com (213.105.172.149) 13.92 ms 11.231 ms 18.204 ms
9 redb-ic-1-so-010-0.inet.ntl.com (62.253.188.106) 13.056 ms 17.211 ms 13.768 ms
10 195.66.224.185 (195.66.224.185) 11.402 ms 16.776 ms 11.315 ms
11 p6-0.core02.jfk01.atlas.cogentco.com (154.54.1.5) 103.978 ms 106.945 ms 112.13 ms
12 p12-0.core02.jfk02.atlas.cogentco.com (66.28.4.169) 101.021 ms 96.942 ms 97.89 ms
13 p15-0.core01.jfk02.atlas.cogentco.com (66.28.4.13) 97.559 ms 100.36 ms 105.198 ms
14 p4-0.core02.dca01.atlas.cogentco.com (66.28.4.81) 103.383 ms 97.089 ms 99.209 ms
15 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.161) 109.458 ms 110.684 ms 108.815 ms
16 p14-0.core01.mco01.atlas.cogentco.com (66.28.4.153) 209.56 ms 236.062 ms 185.888 ms
17 p14-0.core01.tpa01.atlas.cogentco.com (66.28.4.142) 131.522 ms 130.424 ms 131.283 ms
18 p5-0.core01.iah01.atlas.cogentco.com (66.28.4.45) 147.342 ms 147.514 ms 144.147 ms
19 everyonesinternet.demarc.cogentco.com (38.112.12.186) 145.097 ms 145.654 ms 143.904 ms
20 ivhou-207-218-245-121.ev1.net (207.218.245.121) 131.822 ms 130.159 ms 131.268 ms
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 *

12-02-2005, 10:52

No problem here (getting to the web site).
[Edit] ...but a tracert gives the same result you get - maybe one of the hops does not respond to pings?

Toto · 12-02-2005, 11:05

Hi, Welcome to the site.

I can reach the site OK from my ntl BB connection. It may be a proxy problem in your local region, have you tried changing your browser proxy setting to an ntl one outside of your region?

pjcoop · 12-02-2005, 12:05

Hi,

Thanks for your help!
Where would I get a list of NTL proxy servers??

Thanks

Paul

Toto · 12-02-2005, 12:06

Quote:

Originally Posted by pjcoop

Hi,

Thanks for your help!
Where would I get a list of NTL proxy servers??

Thanks

Paul

Here you go, all the best.

http://www.cableforum.co.uk/board/article.php?c=16

Matth · 12-02-2005, 13:42

That is one of the worst routes on NTL.

Another forum - www.driverheaven.net also takes a similar route - poplar UBR to EV1.NET, and it's been slow, slow SLOW for ages.

pjcoop · 12-02-2005, 22:48

Just an update......

Changed proxy server to one of the Watford ones and - bingo - problem solved!
How often do NTL 'reset' or dump the cache on these proxy servers?
I would like to set it back to the default one asap.

Also

How can I bypass the proxy?

Paul

**Paul** · 12-02-2005, 22:58

Quote:

Originally Posted by pjcoop

How can I bypass the proxy?

You cannot bypass ntl's proxies.

Matth · 13-02-2005, 21:13

The only way to "bypass" the default NTL proxy, is to use another NTL proxy, or an outside proxy that is NOT a port 80 proxy - of course, any outside proxies open to everyone, are usually unintentional and overloaded