We've received several emails from customer's of the BT Total Broadband service complaining that the ISP has blocked them from accessing RapidShare, which is an online file hosting/download service (not P2P). Similar issues have occurred in the past, often due to cache conflicts or a restriction imposed by Rapidshare itself, thus we do not believe the problem to be intentional on BT's part.
Precise details are hard to come by, although we believe that the latest issue may in fact be related to a recent BT Home Hub (router) firmware update. Some of the reports indicate that, initially, the problem only affected computers that connected to the hub via Wi-Fi (wireless), although others suggest it has since spread to wired links too.
BT are believed to be aware of the issue, which is hard to check on a Sunday, though there is concern that the operator could drag its feet and take several weeks before issuing a new Home Hub update to fix it. In the meantime here are several things to try, which may or may not circumvent the problem.
Possible RapidShare Fix's
1. Instead of accessing rapidshare with HTTP (e.g.
http://www.rapidshare.com), try accessing it via HTTPS (e.g.
https://www.rapidshare.com) or via just the IP (
http://195.122.131.46 or
https://195.122.131.46/).
2. Access the 'BT Home Hub Manager' (router control panel), go to advanced settings and disable the Firewall (not recommended for security reasons but it is known to work as this is where the bug appears to stem from).
3. Try connecting your computer to the hub via a wired instead of wireless (Wi-Fi) link.
4. Use a third party proxy server to bypass BT's.
5. Edit the HOSTS file (e.g. c:/windows/system32/drivers/etc/hosts) and add the following lines for RapidShare:
195.122.131.46 rapidshare.com
195.122.131.46
www.rapidshare.com
6. Use a different router (not BT's Home Hub).
Please inform us if any of these helped; they are solutions that have worked in the past.
UPDATE - 22nd June 2009:
No response from BT yet, although the issue now appears to be a problem with the operators network rather than their Home Hub as it has been seen to occur on different routers too. So far the HTTPS and HOSTS file solutions seem to be the best workarounds.
