Site access workaround?

[Mike Haven]

I haven't been able to access thehendonmob.com for a week or so.

Just received this e-mail from my ISP:

"Dear Customer.
Thank you for your email
Unfortunately thehendonmob.com has an ip address of 83.245.4.168.
The 83 ip range has been blocked due to the high amounts of spam that is received from these web sites.
sorry for any inconvienice
Kind Regards,
NTL
ntl: Freedom Support Team
ntlworld.com"

Is that it, or is there any backdoor way to access the site without changing my (free) ISP?

Thanks.

[TylerD]

Mike, I'll repost this in THM forum, as they are aware of the problem and have been asking for more details.

[TheHendonMob]

this is our reply from our hosts:

> Hi,
>
> I imagine the issues of NTL users getting to your server are related
> to
> routing issues with them - I'll ensure this gets looked into. Could you
> ask someone on NTL to try a traceroute to your server and let us know the
> results?
>
>> tracert 83.245.4.168
>
> The whole 83.*.*.* range would not have been blocked as this is 16
> milion
> IPs - individual IPs within this range may have but I have checked and
> none of our IP addresses are in any of the major spam lists.
>
> Kind Regards,

the tracert has been done and it would seem that there is a problem on the NTL side. We are only aware of one user with this problem and several NTL users who are fine. If anyone has any further info please feel free to post.

[HendonRob]

Mike,

We've been in touch with NTL and this is the reply we got:

<font color="blue">
Hi,

We are aware that NTL customers are having problems accessing certain websites at the moment, and our faults team are looking into it. I will forward your details to them for further investigation.

If you have any other queries, don't hesitate to contact me again.

Kind regards,
David
NTL Freedom Technical Support
</font>

It's very unlikely their original explanation is true because blocking the entire 83.* range would be an absolutely huge number of websites, and we also have several NTL users who CAN access the site.

Try entering our IP address into your browser address bar, that is:

83.245.4.168

there's a slim chance that might work in the meantime but hopefully NTL will get off their arses and sort out the problem without much more delay.

Rob

[Mike Haven]

Ironically, I have just received another (the third) request from NTL to do a tracert, and also an ipconfig. Because of the latter, I tried the tracert again, and it connected with your site!

So all is well again.

Thank you for your interest and assistance.