Does it bugger up on a nearly continuous basis for everybody else? By bugger up I mean appearing to work perfectly up until the download should start upon which appears a Download-session invalid message. Also get the problems of it thinking I've downloaded stuff when I haven't.
Anybody got any ideas of how to solve this? Seeing as most of the good shit is hosted on RapidShare and all.
Name:
ANon2006-06-02 10:38
Only had that happen when I wait too long to start the download. Try clearing your cache and your history in IE/FireFox/browser
Name:
Anonymous2006-06-02 14:54
Doesn't work for about half the UK these days. Shit sucks.
Someone needs to reroute the page to megaupload.com because their service is better. No one wants to wait 80 minutes between downloads, that's just fucking unnecessary. That and the 60 seconds to wait for a "download ticket". Download tickets are not real. The file is on the server at all times and you could access it at the second the page loads if it let you. There are no queue slots or wait lines needed, Rapidshare always has plenty of speed left over for you and a thousand of your friends.
So why does Rapidshare make you wait? They just want you to buy a premium account. The ones that come in three possible packages that increase at an unfair ratio in favor of Rapidshare.
I noticed lately that the free downloads also stop randomly, making you wait another 80 minutes for nothing. Seriously, people, stop using Rapidshare. The only positive about that service is that files under 10mb you don't have to wait for.
Name:
Anonymous2006-06-09 16:58
Guys, the Rapidshare issue is pretty simple. For ages, ntl has used webcaching, they've got a few big machines that store commonly viewed page, to reduce loading time, they just chuck you their copy.
If you go to a site not on there, or a forced reload thing, the webcache machine will request it from the server. Now, most code will see past the proxy and get your actual ip, and let you download.
However, the coding used in rapidshare's setup is not compatible with the webcache proxy setup used by ntl (AND SOMEWHAT MORE RECENTLY, BT AS WELL), so it only see's the PROXY's ip address.
Hence, it thinks that you're either ALL of BT, and says you've downloaded too much/currently downloading, or it says you're requesting from the wrong ip (the proxy ip requests, your ip receives, it doesn't like that)
If you manually configure your browser/OS to use the http proxy webcache.bt.net:8080 then you won't get the "download session invalid" message. Unfortunately, it will still get you on the first "You have downloaded 50GB Want tod ownload more? Wait till THE END OF TIME".
So you can either enter a mad dash competition with the rest of BT (I've done this a couple of times for stuff I really needed), or you're screwed.
I'm gonna try and get in touch with someone at BT who knows what they're doing (HAHAHAHAHAHA), and tell them to either bypass the proxy for all rapidshare.de connections, or turn the webcache off completely for my connection. After all, my connection was always fine before they turned it on..
Name:
Anonymous2006-06-16 7:07
>>8 Alright, thanks for that. I am on BT so that's hardly unexpected. BT need to get their act together or I'll probably just switch ISPs soon.
The BT webcache is open, you can connect to it from ntl as well.
In fact, I suspect that BT is currently using ntl's webcaches, since they suffer from all the same problems, and BT didn't used to have a webcache setup.
Nah, ntl was running webcache's LONG before BT started; it was about half a year ago, I think.
Plus, ntl and BT don't use the same backbone....
Name:
Anonymous2006-06-20 19:00
oh, for anyone interested, one end or the other has fixed its problem.
the webcache.bt.net:8080 proxy now functions perfectly with rapidshare (at least for me), though the default proxy still fails horribly. But it sucks at everything (banned from /b/, for example) so noone gives a shit about it.