Cable Forum
Page 2 of 2 1 2
Show 100 post(s) from this thread on one page

Cable Forum (https://www.cableforum.uk/board/index.php)
-   Webspace, E-Mail & Browsing Issues (https://www.cableforum.uk/board/forumdisplay.php?f=80)
-   -   NTL Cable users can't access totalbet.com or ukbetting.com (https://www.cableforum.uk/board/showthread.php?t=35882)

Chrysalis 30-09-2005 22:16
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
both worked here, on auto proxies.

Cerberus 30-09-2005 22:43
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Absolutely no problems here. I can access both sites just fine. Bit gutted a few weeks back when I couldn't access this site. :( Missed my fix tbh.

Paul 30-09-2005 22:58
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
I stuck totalbet.com onto my monitor for period tonight and it failed across a range of proxies (33 to be exact) ;

Quote:
30-Sep-2005-22:10:33 : CX80937J : Reply Test for Ashford-1 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:10:40 : CX80957G : Reply Test for Ashford-2 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:18:02 : CX82220E : Reply Test for Cosham-1 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:18:09 : CX82241T : Reply Test for Cosham-2 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:18:16 : CX82261U : Reply Test for Cosham-3 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:18:30 : CX82301Z : Reply Test for Cosham-5 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:18:44 : CX82341B : Reply Test for Cosham-7 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:18:58 : CX82381D : Reply Test for Cosham-9 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:19:05 : CX82401C : Reply Test for Cosham-10 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:23:25 : CX83144J : Reply Test for Leeds-8 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:28:27 : CX84290P : Reply Test for Northampton-1 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:28:34 : CX84320X : Reply Test for Northampton-2 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:28:41 : CX84350E : Reply Test for Northampton-3 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:28:48 : CX84380E : Reply Test for Northampton-4 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:28:55 : CX84410J : Reply Test for Northampton-5 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:29:37 : CX84591D : Reply Test for Nottingham-6 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:29:44 : CX84621Y : Reply Test for Nottingham-7 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:30:20 : CX84772T : Reply Test for Nottingham-12 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:30:34 : CX84832A : Reply Test for Nottingham-14 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:32:12 : CX85255K : Reply Test for Poplar-3 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:32:19 : CX85285D : Reply Test for Poplar-4 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:32:26 : CX85315H : Reply Test for Poplar-5 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:32:33 : CX85345D : Reply Test for Poplar-6 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:32:40 : CX85375U : Reply Test for Poplar-7 on port 8080 failed - Time Out : Count = 2 : Trigger = 3
30-Sep-2005-22:32:47 : CX85405A : Reply Test for Poplar-8 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:32:54 : CX85436T : Reply Test for Poplar-9 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:34:04 : CX85737Y : Reply Test for Southampton-1 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:34:12 : CX85767D : Reply Test for Southampton-2 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:34:19 : CX85797E : Reply Test for Southampton-3 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:34:40 : CX85888T : Reply Test for Southampton-6 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:35:57 : CX86220S : Reply Test for Watford-2 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
30-Sep-2005-22:36:04 : CX86250F : Reply Test for Watford-3 on port 8080 failed - Time Out : Count = 3 : Trigger = 3
I'll try the other site shortly. This is by far the worse result for any site I have ever tested.

nffc 30-09-2005 23:20
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Both work for me, Winnersh proxy though I live Nottm.

Chrysalis 01-10-2005 16:38
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Paul interesting monitor O_o

Paul 01-10-2005 18:21
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Quote:
Originally Posted by Chrysalis
Paul interesting monitor O_o
Yes, and very useful - I monitor all the current ntl proxy servers (every 1/2 hour) normally pointing them at CF, but obviously I can change this.

simbr 01-10-2005 18:47
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
That's a rather bizarre result since multiple proxies from each set are blocked, but at the same time not the entire IP range.


All times are GMT. The time now is 13:46.
Page 2 of 2 1 2
Show 100 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum