Has anyone else had problems downloading torrents on 10.11.2?

[clee290]

I haven't really downloaded anything over the holidays, so this is something I've just started noticing over the past few days. The problem is that I would be downloading something and my Internet (on my Mac) would disconnect for a split second then reconnect. I wasn't sure if it was a problem with my network or my Mac, but I decided to leave it unless it got really annoying (which it did). I did some digging in my router's settings, messed with the Wireless settings on my Mac, but nothing helped. So yesterday I decided to do a fresh install and see what happens.

- Did a fresh install of Yosemite and tested - no problems
- Updated to El Capitan (10.11.0(?)) and tested - no problems
- Updated El Capitan to 10.11.2 and tested - problem has returned!
- Did a fresh install of El Capitan (10.11.0(?)) and tested - again, no problems
- Updated El Capitan to 10.11.1 and tested - no problems

My 'tests' comprised of me downloading Ubuntu twice (a little under 2.5GB total) and hope for no disconnections. So, for the time being, I'll be avoiding 10.11.2 and hope 10.11.3 fixes this problem.

I was just curious if anyone else has experienced problems like this?

 

[Partron22]

uTorrent/BitTorrent in El Capitan

 

[clee290]

uTorrent/BitTorrent in El Capitan

While I appreciate the response, it would have been nice if you had read my post as well It's clearly not the same problem.

 

[fisherking]

tranmission, and no problems in 10.11.1, 10.11.2, or now, 10.11.3 beta...

 

[psik]

tranmission, and no problems in 10.11.1, 10.11.2, or now, 10.11.3 beta...

transmission works flawlessly for me on 10.11.2 ! so no problem for me.

 

[clee290]

Thanks for the responses. I've used Qbittorrent and Transmission and experienced the problem with both clients. Guess the issue is on my end.

 

[Partron22]

It's clearly not the same problem.

It's vaguely related, and I like to collect these things so that two years down the road someone with similar problems will find a possibly useful branch point.

 

[clee290]

It's vaguely related, and I like to collect these things so that two years down the road someone with similar problems will find a possibly useful branch point.

Yea, the only relation being that they're about downloading torrents. While I mean no disrespect, if you're not here to give your input on my problem, I would appreciate if you would start your collection of torrent-problem-related posts elsewhere. Thank you.

 

[Partron22]

Yea, the only relation being that they're about downloading torrents. While I mean no disrespect, if you're not here to give your input on my problem, I would appreciate if you would start your collection of torrent-problem-related posts elsewhere. Thank you.

You are very welcome sir. You may now return to begging for answers to problems which you cannot solve on your own. Good luck!

 

[Riwam]

Yea, the only relation being that they're about downloading torrents. While I mean no disrespect, if you're not here to give your input on my problem, I would appreciate if you would start your collection of torrent-problem-related posts elsewhere. Thank you.

******
Why not just ignore posts which bring you no benefit (something which you never know in advance in sny case)?
Why aswer in such an aggressive and unpleasant way?
Aren't we all supposed to share our thoughts, troubles and efforts to help each other (or at least try to help)?
Let's try to keep friendly in this forum.

 

[KALLT]

I do not have that problem myself and it is difficult to help you without having more information to go on. So you are saying that without any other changes, the issue only appears on 10.11.2, regardless of the torrent client? Have you checked your firewall settings as well? Have you changed your network settings aside from the OS defaults (e.g. DNS)?

You may want to send a bug report at bugreport.apple.com. If you can, you could try the beta of 10.11.3 at beta.apple.com to see whether the issue is there too.

---

You are very welcome sir. You may now return to begging for answers to problems which you cannot solve on your own. Good luck!

Uncalled for.

******
Why not just ignore posts which bring you no benefit (something which you never know in advance in sny case)?
Why aswer in such an aggressive and unpöeasant way?
Aren't we all supposed to share our thoughts, troubles and efforts to help each other (or at least try to help)?
Let's try to keep friendly in this forum.

I see no aggression on the OP’s part, the response was acceptable (and IMHO also necessary).

 

[Partron22]

Uncalled for.

Nah. He's just asking for someone to fix only his screwup, (it seems everyone else can get Transmission to work), without any possibility of anyone with similar problems benefiting from the problem solving process. If he wants to be treated as a special princess, and get personal only service, I'll give it to him. Of course that service will be nothing, because no matter what he gets, he's likely to bitch about it. I don't need the aggravation, and if you've sense, you don't either the aggravation either KALLT. Well, maybe if he wants to pay a couple hundred an hour, but if he were willing to do that he'd take the Mac he messed up to the local repair store, and he obviously feels entitled to be given a free solution here.

 

[steve62388]

I'm fairly sure despite all the innumerable attempts Apple haven't quite fixed the Wi-Fi issues that emerged a few OS X versions ago, despite reverting back to mDNSResponder. https://www.macrumors.com/2015/05/26/apple-discoveryd-replaced-with-mdnsresponder/

Since the switch to Discoveryd my Macs have never been the same with similar Wi-Fi drops to yourself. I would be willing to bet your connection is dropping briefly whilst just internet browsing too, it's just that most of the time you don't notice it because your connection is idle. On the other hand your torrents throw a wobbly.

Apple knows there is a problem, pretty much every OS X release includes some sort of Wi-Fi bug fix these days.

 

[KALLT]

I'm fairly sure despite all the innumerable attempts Apple haven't quite fixed the Wi-Fi issues that emerged a few OS X versions ago, despite reverting back to mDNSResponder. https://www.macrumors.com/2015/05/26/apple-discoveryd-replaced-with-mdnsresponder/

Since the switch to Discoveryd my Macs have never been the same with similar Wi-Fi drops to yourself. I would be willing to bet your connection is dropping briefly whilst just internet browsing too, it's just that most of the time you don't notice it because your connection is idle. On the other hand your torrents throw a wobbly.

Apple knows there is a problem, pretty much every OS X release includes some sort of Wi-Fi bug fix these days.

I was thinking about that as well. Apple may still be tweaking the WiFi capabilities, but I am not aware of any notable changes in that area for 10.11.2. If it is purely a clean install that causes this problem then the OP is likely correct in saying that it lies in the OS.

OP: Are there any other areas where this problem might be occurring? Video streaming or regular file downloads perhaps?

Nah. He's just asking for someone to fix only his screwup, (it seems everyone else can get Transmission to work), without any possibility of anyone with similar problems benefiting from the problem solving process. If he wants to be treated as a special princess, and get personal only service, I'll give it to him. Of course that service will be nothing, because no matter what he gets, he's likely to bitch about it. I don't need the aggravation, and if you've sense, you don't either the aggravation either KALLT. Well, maybe if he wants to pay a couple hundred an hour, but if he were willing to do that he'd take the Mac he messed up to the local repair store, and he obviously feels entitled to be given a free solution here.

All I see is you being pissed-off. Pull yourself together.

 

[Partron22]

Yeah, kallt, I'll just let someone else answer the question. I bet if he figures it out for himself, he won't give us the courtesy of explaining what was wrong and how he fixed it. Thread's not worth my time.

 

[Riwam]

Yeah, kallt, I'll just let someone else answer the question. I bet if he figures it out for himself, he won't give us the courtesy of explaining what was wrong and how he fixed it. Thread's not worth my time.

*********
Don't lose your nerves about the unfriendliness found in this thread and ignore KALTT. He is the kind of person who believes he knows everything better than others and he can add countless posts without ever ending it, although they bring no use to anybody.
At a certain moment it's better just not to answer any more and quit the thread.
One should keep one's nerves and one's time for better uses IMHO.
Ed

 

[Partron22]

That's what I'm doing Riwan. It's far more fun helping people whose USB went south for no apparent reason than dealing with odd personal issues. Having started in assembly w a Rockwell 6500, working up thru an apple II and III, and countless Macs since then I probably know a thing or two kallt doesn't. Anyway he doesn't bother me. What pisses me off is rude questioners. It's not as if any of us, except maybe Weaselboy, get paid for this, and that's just because he has a nice name/favicon.