Problems loading web pages
Discussion
I seem to be getting a lot of "Cannnot find server" errors, when surfing. Over the last week, I have noticed an awfull lot my attempts just fail. Sometimes, I visit a site and half hour later, it's not there. I feel like half the WWWeb has gone ! or NTL are blocking half the sites or something ?
Anybody want to help me out. Any 'Intenet Options' experts out there? Know of any programs to check my connections/throughput ?
I use the Zone Alarm firewall on my NTL broadband, and could really do with some help.
Thanks
Regards John S
Anybody want to help me out. Any 'Intenet Options' experts out there? Know of any programs to check my connections/throughput ?
I use the Zone Alarm firewall on my NTL broadband, and could really do with some help.
Thanks
Regards John S
Sounds familiar...
Speed test:
===========
http://bandwidthplace.com/speedtest
Help with setting up etc:
=========================
http://broadband-help.com
Hope this helps..
Speed test:
===========
http://bandwidthplace.com/speedtest
Help with setting up etc:
=========================
http://broadband-help.com
Hope this helps..
Tried again and it loaded
Done the speed test and got 380.2 k/s and 46.4k/s
Not too bad I supose
Still coundn't get into the http://broadband-help.com/ page
Anymore suggestions ?
Thanks

Done the speed test and got 380.2 k/s and 46.4k/s
Not too bad I supose
Still coundn't get into the http://broadband-help.com/ page

Anymore suggestions ?
Thanks
You could try www.speedguide.net on left goto BROADBAND > BROADBAND TOOLS > ANALYZER
If you are using Broadband that is.
Just re-read post , so yes you are
>> Edited by trevorw on Friday 19th September 21:43
If you are using Broadband that is.
Just re-read post , so yes you are
>> Edited by trevorw on Friday 19th September 21:43
John_S4x4 said:
Tried again and it loaded ![]()
Done the speed test and got 380.2 k/s and 46.4k/s
Not too bad I supose
Still coundn't get into the http://broadband-help.com/ page![]()
Anymore suggestions ?
Thanks
your broadband is very slow for 512K.
I've just run the test on mine (freedom2surf) and got 480.2K
I've been having similar issues to you. I'm also on NTL's broadband and have noticed issues mainly getting to sites in the US but occasionally in the UK (including Pistonheads too). I upgraded to IE6 a few weeks ago and don't know if it is related to that or not. However now that I've seen I'm not the only one Perhaps it is time for an email to NTL customer support ?
te51cle - Seems we have a common problem. I would more than likely agree about the US thing. I also upgraded to IE 6.0 a short while back. Looks like we are in the same boat. I seem to go surfing and every other link seems to be dead
I'll try and have a look on some of the NTL Cable forums (Chetnet etc)to see if the problem has come up. If you find out anything, please let me know too
Regards John S

I'll try and have a look on some of the NTL Cable forums (Chetnet etc)to see if the problem has come up. If you find out anything, please let me know too
Regards John S
Done another speed test
Section 1: General Ping Results
A Ping test is the time taken for a server to reply to a request
ntl:World Server:
21ms - Normal - it's about right!
UK Server 1 (www.demon.net):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 194.159.254.213 over a maximum of 20 hops
1 9 ms 9 ms 11 ms 10.152.183.254
2 10 ms 10 ms 15 ms 62.253.122.149
3 12 ms 9 ms 9 ms 62.253.121.129
4 9 ms 22 ms 9 ms 62.253.184.117
5 15 ms 9 ms 10 ms 62.253.185.201
6 10 ms 13 ms 12 ms 62.253.185.86
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
Trace complete.
UK Server 2 (www.bbc.co.uk):
29ms - Normal - it's about right!
UK Server 3 (www.ic24.net):
13ms - Excellent - better than expected
USA East Coast Server (www.yahoo.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 64.58.76.176 over a maximum of 20 hops
1 8 ms 9 ms 11 ms 10.152.183.254
2 7 ms 6 ms 14 ms 62.253.122.149
3 13 ms 193 ms 12 ms 62.253.121.129
4 12 ms 11 ms 9 ms 62.253.184.117
5 9 ms 10 ms 11 ms 213.105.172.161
6 14 ms 26 ms 11 ms 166.63.161.229
7 12 ms 11 ms 18 ms 166.63.209.205
8 95 ms 97 ms 95 ms 206.24.226.99
9 206.24.238.38 reports: Destination host unreachable.
Trace complete.
USA West Coast Server (www.lycos.com):
92ms - Fast - very fast response
European Server (www.marcopoly.com):
14ms - Excellent - better than expected
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 2: Custom Server Ping Results
These results are to four user-definable servers.
Blueyonder Counter-Strike 1:
21ms -
Blueyonder Team-Fortress Leage 1:
22ms -
BarrysWorld Master Server (all games):
18ms -
Japanese Ping Server (VERY long distance!):
18ms -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 3: Download Speed Results
Three downloads are tested; one from one of your ISPs servers, one through your Transparent Cache and one through an alterntive cache. This will give you an idea of how capable your connection is. Note: You should take the highest download speed into account.
ntl:World - 512k service Server Download:
73KB/s (584Kb/s) - Superb - much higher than expected
Download through Transparent Cache:
78KB/s (624Kb/s) - Superb - much higher than expected
Download through alternative Cache (webcache.blueyonder.co.uk):
0KB/s (0Kb/s) - **** SERVER ERROR: Unexpected error from Server****
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 4: Packet Loss
50 Ping Requests are sent to your server. The packet loss is measured by how many of the packets don't bounce back to the client. High packet loss may slow down your connection.
50 packets were sent, 50 bounced back; 0% loss (estimated)
Fantastic - no packets dropped!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 5: Transparent Cache Page Fetch Time
This test times how long your Transparent Cache takes to fetch a page from the Internet. Please note that this test is subject to many different parameters and sometimes may not be 100% accurate. This test can be used to show delays when trying to view Internet sites. The timing takes place from the moment the request for the file is sent to the moment the proxy server responds.
Average time taken to retrieve a page: 9ms - Fine, nothing to worry about
Section 1: General Ping Results
A Ping test is the time taken for a server to reply to a request
ntl:World Server:
21ms - Normal - it's about right!
UK Server 1 (www.demon.net):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 194.159.254.213 over a maximum of 20 hops
1 9 ms 9 ms 11 ms 10.152.183.254
2 10 ms 10 ms 15 ms 62.253.122.149
3 12 ms 9 ms 9 ms 62.253.121.129
4 9 ms 22 ms 9 ms 62.253.184.117
5 15 ms 9 ms 10 ms 62.253.185.201
6 10 ms 13 ms 12 ms 62.253.185.86
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
Trace complete.
UK Server 2 (www.bbc.co.uk):
29ms - Normal - it's about right!
UK Server 3 (www.ic24.net):
13ms - Excellent - better than expected
USA East Coast Server (www.yahoo.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 64.58.76.176 over a maximum of 20 hops
1 8 ms 9 ms 11 ms 10.152.183.254
2 7 ms 6 ms 14 ms 62.253.122.149
3 13 ms 193 ms 12 ms 62.253.121.129
4 12 ms 11 ms 9 ms 62.253.184.117
5 9 ms 10 ms 11 ms 213.105.172.161
6 14 ms 26 ms 11 ms 166.63.161.229
7 12 ms 11 ms 18 ms 166.63.209.205
8 95 ms 97 ms 95 ms 206.24.226.99
9 206.24.238.38 reports: Destination host unreachable.
Trace complete.
USA West Coast Server (www.lycos.com):
92ms - Fast - very fast response
European Server (www.marcopoly.com):
14ms - Excellent - better than expected
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 2: Custom Server Ping Results
These results are to four user-definable servers.
Blueyonder Counter-Strike 1:
21ms -
Blueyonder Team-Fortress Leage 1:
22ms -
BarrysWorld Master Server (all games):
18ms -
Japanese Ping Server (VERY long distance!):
18ms -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 3: Download Speed Results
Three downloads are tested; one from one of your ISPs servers, one through your Transparent Cache and one through an alterntive cache. This will give you an idea of how capable your connection is. Note: You should take the highest download speed into account.
ntl:World - 512k service Server Download:
73KB/s (584Kb/s) - Superb - much higher than expected
Download through Transparent Cache:
78KB/s (624Kb/s) - Superb - much higher than expected
Download through alternative Cache (webcache.blueyonder.co.uk):
0KB/s (0Kb/s) - **** SERVER ERROR: Unexpected error from Server****
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 4: Packet Loss
50 Ping Requests are sent to your server. The packet loss is measured by how many of the packets don't bounce back to the client. High packet loss may slow down your connection.
50 packets were sent, 50 bounced back; 0% loss (estimated)
Fantastic - no packets dropped!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 5: Transparent Cache Page Fetch Time
This test times how long your Transparent Cache takes to fetch a page from the Internet. Please note that this test is subject to many different parameters and sometimes may not be 100% accurate. This test can be used to show delays when trying to view Internet sites. The timing takes place from the moment the request for the file is sent to the moment the proxy server responds.
Average time taken to retrieve a page: 9ms - Fine, nothing to worry about
Just thought I'd add to my post here and also add another to the post counter
Might of found the solution
"..use a proxy use 62.255.32.5
The only thing I have set up a little differently here is that for my primary dns I use the ntl default of 192.168.8.100 but for secondary dns I use 195.92.195.94 "
Will give this a go
Regards John S

Might of found the solution
"..use a proxy use 62.255.32.5
The only thing I have set up a little differently here is that for my primary dns I use the ntl default of 192.168.8.100 but for secondary dns I use 195.92.195.94 "
Will give this a go
Regards John S
When I was on NTL (in Guildford), their inktomi web caches and DNS servers would go down on a regular basis.
http://homepage.ntlworld.com/robin.d.h.walker/cmtips/trancache.html#ntl
Here's a list of ntl network proxy servers, try putting one of those into the IE options to see if you have any luck. I also used to use webcache.bt.net:8080, but I'm not sure if that works anymore for outside access.
http://homepage.ntlworld.com/robin.d.h.walker/cmtips/index.html is generally a good site for NTL/cable modem issues
http://homepage.ntlworld.com/robin.d.h.walker/cmtips/trancache.html#ntl
Here's a list of ntl network proxy servers, try putting one of those into the IE options to see if you have any luck. I also used to use webcache.bt.net:8080, but I'm not sure if that works anymore for outside access.
http://homepage.ntlworld.com/robin.d.h.walker/cmtips/index.html is generally a good site for NTL/cable modem issues

If you keep having this prob with a known fav site of yours ie one min its there then its unavailable, Ping it and keep a copy of its IP address. Next time its unavailable try to get to it via IP to rule out DNS or not. It could well be that your DNS server settings are in wrong order or have a tendancy to go down rather a lot...there are free public DNS servers you could try using if this is the case, just google to get the addresses..
I have also had these problems with yahoo and ebay, ntl help said its due to problems with Microsoft upgrading something or other.
Seems strange that only ntl are having problems.
I got 902kb on the connection test!
UPDATE
Rang NTL (waiting for an hour) and in the control panel, go to Internet Options, Connections and lan Settings. In the bottom bit Proxy setings enter 62.253.128.4 and port 8080.
This works for me!
>> Edited by gtir on Monday 29th September 13:51
Seems strange that only ntl are having problems.
I got 902kb on the connection test!
UPDATE
Rang NTL (waiting for an hour) and in the control panel, go to Internet Options, Connections and lan Settings. In the bottom bit Proxy setings enter 62.253.128.4 and port 8080.
This works for me!
>> Edited by gtir on Monday 29th September 13:51
gtir said:
I have also had these problems with yahoo and ebay, ntl help said its due to problems with Microsoft upgrading something or other.
Seems strange that only ntl are having problems.
I got 902kb on the connection test!
UPDATE
Rang NTL (waiting for an hour) and in the control panel, go to Internet Options, Connections and lan Settings. In the bottom bit Proxy setings enter 62.253.128.4 and port 8080.
This works for me!
>> Edited by gtir on Monday 29th September 13:51
I have just spent an hour on the phone to NTL and got the same info!
Wish I'd have seen this before abusing my phone bill!
The proxy settings work for me too.... but the support person I spoke to tried to tell me that it wasn't NTL that was at fault, it was the sites I was visiting.
When I asked him if Ebuyer.co.uk, Multimap.com, Hotmail.com all failed at the same time, he couldn't answer.....
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff