Re: 403 Forbidden
 

Sorry boss, I was only trying to help :( :)

Re: 403 Forbidden
 

:LOL: Was only messing..... I've done the same thing more times than I care to think about :)

:hugs:

Re: 403 Forbidden
 

See, I had to check if all the steps were correct as well, so as to not confuse the OP :)

Re: 403 Forbidden
 

right so if i get those type of messages in the future i will try changing proxy servers, cheers everyone

Re: 403 Forbidden
 

Nice to know that you're looking after me and the OP so well :tu: You're doing a stirling job, keep it up :D
__________________

Yep, always worth a try at changing the p(r)oxy server.

Best bet (before you go to too much trouble) is to see if anybody else can access the site. If nobody can get to it then it's probably down. If you're the only one that can't then it's worth doing the proxy shuffle.

Don't forget that you currently have one enabled though, always worth turning the current one off before you go trying any new ones, just in case it's that that is causing the problem.

Re: 403 Forbidden
 

this is a general request -

please do not specify a proxy server unless absolutely necessary

having thousands of users specifying particular proxies really ballses up the load balancing- if there are issues they are normally caused by crap website coding meaning that the proxy ip is detected instead of the real ip- resulting in a ban.

I give up on sites that don't bother implementing [simple] scripts that detect the actual visitors ip instead of a proxy server.

If you have problems with a particular site it is best to raise this to ntl who can then negociate with a site admin if necessary to get a proxy removed from a ban list- the UK's biggest broadband ISP have a lot more bargaining power than an individual user ;)

Re: 403 Forbidden
 

:shrug:

<Edit>

Whilst I understand the setiment behind the post, and appreciate that you are trying to make people aware that simply selecting an alternate proxy is not the best resolution to all their problems, I would have to question whether or not your average user will really be interested in NTL's load balancing issues.

They pay for a service, the service fails to delivery what it should (or at least, that's their perception, so they take steps to correct that (by setting a proxy manually). From their point of view, problem solved. However I appreciate that this "ballses" things up from NTL's point of view.

If this is a serious issue for NTL then perhaps they should be taking steps to overcome it?

</Edit>

Re: 403 Forbidden
 

I'm with Raistlin - if I want to view a site, then I'll change proxy so I can. There have long been problems with some sites, notably Yahoo, and nothing has changed. Likewise, there have long been problems with NTL proxy servers, and little has changed. Sometimes the transparent proxy just stops functioning correctly :shrug:

Re: 403 Forbidden
 

I agree with what you are saying, but if problems are not reported to ntl who can they even begin to do something about it? I have escalated a lot of proxy problems through this site [which btw takes a lot of my own time because i have to test at least two whole ranges of proxies before escalating, and have to do it in my own time] and i don't begrudge doing it, but i am just trying to get the point across that ntl need to know about problems in order to fix them.... it is completely unrealistic for ntl to test every single site through every single proxy 24hours a day.........

Re: 403 Forbidden
 

Perhaps NTL should be looking at a better solution than simply relying on the good will of one man to test two whole ranges of proxies in his own time (thanks by the way)?

Surely there must be some change that they can implement within the underlying technology that prevents these problems from happening in the first place? Although I could be wrong, I obviously don't fully understand the technology.

Like green says, this has been a problem with the transparent proxies for as long as I can remember - you'd think that they would have tried to do something about it by now.
__________________

Anyway, the idea of phoning NTL to tell them that I can't access one website out of the millions that are available is just laughable.

Re: 403 Forbidden
 

MB - I have a lot of respect for you and your attitude to customer services is exemplary, but you're in the minority. I know from where I work that if a customer gets a new guy, the chances of successful problem resolution are slim, especially if it's a weird problem that requires experience to solve it. I also know that the majority of staff where I work are stats driven, and care little for customer service. There's a thread on this forum where it seems highly likely that the poster spoke to a new NTL tech, who didn't have a clue. At the moment, I'm have no confidence that phoning NTL to report that I cannot, or have problems, accessing a website will result in anything. Recently I had problems with my connection and after speaking to another NTL employee on this site, I decided to do nothing, as he suggested, and let the network monitoring folks detect the problem, which they seem to have done (unless the problem has resolved itself). I don't honestly believe a tech on the phone would have helped - partly because all the CM lights were on. IME, lights on = no problem. I've basically lost confidence and I'm a tough cookie to get fifth+ chances out of :)

:Peaceman:

Re: 403 Forbidden
 

i see your point.... but bear in mind i am just one of the people at the end of the phone....

there are those who care and those who don't, and that will be the way with any company...

anyway this has gone off topic now... the OP's problem was resolved [or at least bodged] so i think any other comments can be taken to PM if need be (as i have done with other members in this thead, who seem now seem intent on making [not so] subtle digs at me in the public forum....)

I agree partially with what you were saying, but the point i was trying to make is that "bodging" only works in the short term, and does not help resolve long term issues- if ntl were inundated with calls about proxy problems maybe they would do more to resolve them :shrug:

Re: 403 Forbidden
 

Normally I recommend always using a proxy from your local group (unlike others who, e.g., always give the same manchester one). In this case though, it seems they have set up a rule on the webserver itself that blocks the IP range of the whole lutn set.

Re: 403 Forbidden
 

site loads here but very very slow, seems they got issues on the server/provider.