transmission block internet connection

[joansalo]

I'm using last version (1.42) of transmission on a one year old Macbook with 10.5.6 OS, and a wifi connection. I've been having some problems with transmission blocking my internet connection to the point that when I open the program the other applications using interntet (mail app., viena and web browsers) don't work or do it very slowly. But the problem has reached such a level that sometimes it blocks all wifi from my flat (and the other 3 computers connected to it suffer the same problem). I've been cheching all recomendations from the help menu in Transmission. The points I've focused on are:

- Firewall: is desactivated, so there should be no problem.
- Ports: I'm using the automate port forwarding and it gives me green light, I've also opened a port for the app thats suposed to be working (I've checked it with the app and with yougetsignal.com)
- Upload and download speed: I've capped to an apropiate speed so it doesn't flood my connection.
- Transfers queued: I've got not more than 3 files downloading and 3 uploading simultaniously.

I've got a good internet service and I'm quite surprised that this can happen (it has happend a few times before) and I'm pretty sure it's not a problem of that cause I download quite often quite heavy files from internet and there are no problems with the connection being flooded. Does anybody has a recomendation? Has anybody suffered the same problem?

Thanks in advance
PD. Sorry for my english but I haven't practiced for a while

[fredash]

Hi,

I use Transmission since version 1.40, and i always have had these same types of problems !
I dowloaded the latest beta (1.50 bêta), and the problem persists.

(iMac Core Duo, Mac OS X 10.5.6)

Fred.

[brokenshoes]

I have the same issue too. But my downloads don't even start, I open the program with all my downloads paused and my internet crashes. It worked fine up until about October then this started. I stopped downloading until I got to my parents house, it worked fine. I came back home and it worked for a week then this started again. All the same things as the OP; reasonable speed settings, open port, 3 downloads going at the same time maximum, etc. etc.

Is it a bug, maybe?

MacBook 10.4.11. Transmission version 1.42 and previously having the exact same issue on 1.30

[livings124]

http://forum.transmissionbt.com/viewtop ... f=4&t=3274

[aryayush]

So this was the reason my Internet connection was getting screwed up every time I started using BitTorrent. And here I was, blaming everything and everyone from my Internet service provider to my router and Time Capsule and even Mac OS X.

Damn it!

I’m switching to µTorrent.

[aryayush]

OK, Transmission wasn’t the cause of the problem. I tried using µTorrent on my Mac and am facing the same problem.

Notably, this problem doesn’t surface both when I download using the standard HTTP protocols and when I download from the BitTorrent network via µTorrent on Windows Vista (on the same Mac powered by the same Internet connection using the same combination of a modem and Time Capsule).

So what the heck is going on here? Has anyone figured out what might be causing this? Is Mac OS X itself the problem?

[aryayush]

Don’t get me wrong, I’ve been a Transmission evangelist for over two years now and still love the application dearly.

It’s just that for the past two weeks I’ve been facing so many problems with my Internet connection and have called my ISP’s support executives to my house so many times that my patience was wearing thin. I’ve replaced my modem and my Time Capsule and restarted my Mac more times than I would care to count.

And then I tried downloading using µTorrent on Windows Vista and didn’t face any issues. Furthermore, as soon as I searched for this problem on Google, this was the first hit, and it seemed like this had to be the reason I’d been suffering for the past two weeks.

So I had a knee-jerk reaction. It wasn’t anything against Transmission. In fact, the only reason I was so incensed was precisely because I’ve been advocating Transmission to anyone who’d listen for the past two years.

As soon as I figured out that it wasn’t the cause, I made it a point to return to the forum and inform others as well, so that other people wouldn’t be misled like I’d been.

What else do you expect from me? If you’ve never made a wrong judgement about anything in your life, then sure, feel free to ridicule me; but something tells me that is not the case.

All that said, I realise that as one of the developers of Transmission, you might not want to hear people post false information about your product and I apologise for unintentionally having done so.

-------------------

Now, if you can proffer me some advice on how to fix this, I sure could use it. Thanks.

[Jordan]

So this was the reason my Internet connection was getting screwed up every time I started using BitTorrent. And here I was, blaming everything and everyone from my Internet service provider to my router and Time Capsule and even Mac OS X.

Damn it!

I’m switching to µTorrent.

OK, Transmission wasn’t the cause of the problem. I tried using µTorrent on my Mac and am facing the same problem.

So what the heck is going on here? Has anyone figured out what might be causing this?

I think what's going on here is that you're trying to kill the Transmission devs by making us laugh ourselves to death.

[edit] The problem you describe is usually caused by a router being overwhelmed by the number of short-lived connections that p2p generates. Googling for BitTorrent + router + (your router) may help.

[aryayush]

Thanks.

But why doesn’t it happen when I use BitTorrent on Windows Vista? And how likely is it that this problem will persist across two routers from different companies?

[livings124]

But why doesn’t it happen when I use BitTorrent on Windows Vista?

Something with the setup on your mac?

[aryayush]

Thank you, everyone, for all the help and information.

I figured out the problem: I was unable to get any of the ports I was using forwarded successfully so I’d used 5190 as the port in Transmission (it was the port iChat had been assigned and was open). I’d done the same thing on µTorrent for Mac but not on µTorrent for Windows. As soon as I changed the port back to some random number, the problem got sorted out. I still have a closed port out here that I’ve no idea how to get around, but at least it works now.

Once again, I would like to remind readers of this thread (and the people who’d posted here before I did—‘brokenshoes’, ‘fredash’, and ‘joansalo’) that this problem had nothing whatsoever to do with Transmission, which still works just as perfectly as it always has.