junkiebob

I used to have the same problem with another computer, what helped for me then was setting the Global Maximum Download Speed to something beneath my full bandwith instead of limitless.

Yeah, I think so too, because if everyone stops ONCE they get a new scrape. All right that might take some time, but probably not hours, right? That would mean there are several stages of disconnecting then: 1. Seed disconnects and sends message to tracker 2: Everyone in the swarm keeps connecting UNTIL they get a new listing after re-connecting to tracker 3. Some people KEEP connecting, even if they know I'm not in the list anymore after they re-connected to tracker Just borrowed some technical terms from you guys there :D Do you think this is what happens?

Thanks for your reply bitdave :) I tried your suggestions. Unfortunately I don't think my ISP gives dynamic IP's. TcpView is a pretty nifty little program and it did give some more info. I can now clearly see all those BitComet connections and see them disappear when I stop the torrent, like you said. When every last one of 'em is gone and I shut down BitComet, there seem to be no 'BitComet-related' connections left. However right from the moment I shut down BC, I still get those alerts. In addition, I tried tweaking connection settings. But this also didn't help, since it's an after-BC-shutdown situation with effectively no connections, only connection attemps. Do you think leaving BC on longer - without running torrents - will help to send out the message I'm off? Too bad there is no SIGN OFF button to let the network know you're quiting, of course normally EXIT would be that button. Naturally these alerts are a mere annoyance, rather than a real problem, but I'd like to minimize as much as possible. Cause in a couple of days I already got a whopping 5000 ZA alerts of which probably 99% was due to this BC issue. Thanks :) In a more general sense, what results in this issue and what is the advantage of such a connection method? I mean, wouldn't signing off people who aren't available any more be a lot more effective? Now a lot of 'connection-space' is lost, when 1 signal from a seeder to a server, would avoid all these hundreds of connection attemps. Don't know much about the technical details of the process though, so maybe I'm talking BS here :D

Hi guys, I have an issue I can't resolve concerning Zone Alarm in combination with BitComet. I've searched everwhere, read the FAQ's, searched the forums, but I can't really find anything about this issue. I've been using BitComet for quite a long time, but recently I installed Zone Alarm Pro (version: 6.5.700.000) which resulted in massive amounts of alerts for the BitComet port, hours after closing BitComet. So everything works fine, torrent's, download / upload speeds are all right. But when I shut down BitComet, I keep getting firewall alerts in Zone Alarm mainly of the following kind: TCP (flags: S) towards my IP including the port used by BitComet. Now if this keeps up maybe 5 min after shutting down BitComet, ok, but this goes on hours and hours. When I turn on the computer the next day, people are still continuously trying to connect to my computer at that BitComet port. There are no other 'intruder attempts', I use ZoneAlarm firewall, AVG Free virus scanner, Ad-aware, Spybot & HijackThis and my computer is completely clean (and working like a charm). My question is: How can I stop this massive amount of people trying to reach me hours after closing BC? Is there anything I can do about this by changing settings or something? Thanks a lot for your time and effort! :)