Cable Forum

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)

Teamtalkmedia 30-09-2005 17:20
NTL Cable users can't access totalbet.com or ukbetting.com
 
Ok first let me say that I am not an NTL cable user but I am posting this message on behalf of NTL users who are having this problem. This really is pulling at straws but the NTL fault service is so bad I have no choice.

I work at a company called Teamtalk media who run various sporting websites.
In the last week its become apparent that NTL users are increasingly unable to access totalbet.com and ukbetting.com, which we run and we have had around 200 people phone in with this problem since last sunday. :td:

Trying to get through to NTL to report the problem is a complete waste of time. I can't even get hold of a number other than the technical fault helpline to report it. I have logged it with technical support but they can't tell me when its fixed so I have no way of knowing when its sorted.

If your on NTL broadband and can try the following links in your browsers I'd be grateful.

http://www.totalbet.com

http://www.ukbetting.com

If your a technitian for NTL can you please pass this fault on to the relevant people in your company. We don't want to have our(and your) customers waiting for an hour in the que on your support line to report this - As instructed by one of your engineers I talked to. Its beyond rediculous!:mad:

Thanks

Tim Jefferies

marky 30-09-2005 17:23
Re: Cable users can't access totalbet.com or ukbetting.com
 
Works for me so :shrug: even though i would never use them

AndrewJ 30-09-2005 17:23
Re: Cable users can't access totalbet.com or ukbetting.com
 
Hiya :welcome: I can access both sites easily and am on NTL.

MovedGoalPosts 30-09-2005 17:23
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Moved to Proxy Discussion

IanUK 30-09-2005 17:24
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Neither work here - good old Poplar proxies again :(

MovedGoalPosts 30-09-2005 17:26
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
:welcome: TeamtalkMedia to Cable Forum :D

Does this statement from ntl have any relevance to your situation? http://www.cableforum.co.uk/board/sh...ad.php?t=35790

sirsimon 30-09-2005 17:30
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
no accessin problems here neither can reach both sites in under 1 second

Teamtalkmedia 30-09-2005 17:32
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Ah, so its a proxy problem. Great stuff NTL. Great phone support great technical help. Just great. I'll pass this info onto our phone center. I shall also let phoning in NTL customers know what they've got themselves into.

This is rediculous its NTL's job to do this! I'm doing NTL's job! :dunce:

hello cable forum! :disturbd:

Paul 30-09-2005 17:33
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Both fine here, with a bloody annoying pop-up when you close them.

SLM 30-09-2005 19:29
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Quote:
Originally Posted by Teamtalkmedia
Ah, so its a proxy problem. Great stuff NTL. Great phone support great technical help. Just great. I'll pass this info onto our phone center. I shall also let phoning in NTL customers know what they've got themselves into.

This is rediculous its NTL's job to do this! I'm doing NTL's job! :dunce:

hello cable forum! :disturbd:
So in the same text do you offer or pass on details of people that have betting addictions to the relevant authorities. I have a friend that lost everything to gambling so the more people that can not get on to your site the better IMO.

Paul 30-09-2005 19:45
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Stay on topic please, this is not a thread about the merits of gambling. Off topic posts are liable to deletion.

Teamtalkmedia 30-09-2005 19:45
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Quote:
Originally Posted by SLM
So in the same text do you offer or pass on details of people that have betting addictions to the relevant authorities. I have a friend that lost everything to gambling so the more people that can not get on to your site the better IMO.
I also know someone who lost £80,000 due to a gambling addiction. They went bankrupt. However, my job is to work for this company and I work for them - to earn. So, I'm simply doing my job.

Betting is actually a very small division of the Teamtalk media group. We deal with much more besides - Teamtalk.com, football365.com, sportinglife.com, itv-football.com, boxing on itv, radio stations for adsa, pcworld, makro etc... content delivery for any major sport related web sites..."fingers in many pies" as my manager puts it! :p:

Please do not troll this thread. If you want to discuss this further send me a PM

JohnHorb 30-09-2005 19:51
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Quote:
Originally Posted by Teamtalkmedia
Ah, so its a proxy problem. Great stuff NTL. Great phone support great technical help. Just great. I'll pass this info onto our phone center. I shall also let phoning in NTL customers know what they've got themselves into.

This is rediculous its NTL's job to do this! I'm doing NTL's job! :dunce:

hello cable forum! :disturbd:
I think if the NTL statement is correct, the problem with proxies is due to lazy programming on the web sites affected, i.e. they don't bother to look at the end client IP, just the proxy, then think they are suffering a denial-of-service attack and block the proxy ip. IF this is the case, its a teamtalk problem, not NTL's.

IanUK 30-09-2005 20:06
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Quote:
I think if the NTL statement is correct, the problem with proxies is due to lazy programming on the web sites affected, i.e. they don't bother to look at the end client IP, just the proxy, then think they are suffering a denial-of-service attack and block the proxy ip. IF this is the case, its a teamtalk problem, not NTL's.
No, its us the poor NTL customers problem, we are stuck in a no mans land of non working sites and slow access :(

Basically the argument seems to be that either the whole web changes to accomodate NTL or NTL changes...hmmm tricky one that.
Yes there are standards, and yes designers should stick to them , but they don't and many sites simply don't work on NTL that work elsewhere, thats without taking into account the whole 'false denial of service blocks proxies which in turn blocks whole areas of the country' thing

Chris W 30-09-2005 20:28
Re: NTL Cable users can't access totalbet.com or ukbetting.com
 
Quote:
Originally Posted by Teamtalkmedia
<snip>
do you have access to the logs from your site?

If so, you can probably see which ranges of ntl proxies are unable to access your site; passing this information to me via PM would be appreciated :)

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 18:09.

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