I can download a torrent just fine, and when downloading I don't have any problems uploading, but for some reason I can't reliably start any torrents that I create myself. The symptom is that remote users are disconnected after less than a second.

I'm on Ktorrent 2.2.1 using KDE 3.5.7 release 72.6 on openSUSE 10.3. My NAT router has ports 6881-6999 (TCP) and 4444 (UDP) forwarded. I've tried disabling openSUSE's firewall and still no luck.

Curiously, I didn't have a problem with Ktorrent in FreeBSD 7.0 on the same computer, or with Transmission on a Mac behind the same NAT router.

Any ideas?

P.S. Here's what the logfile looks like:

Sun Mar 30 20:08:51 2008: Authentication(S) to xxx.xxx.xxx.xxx : ok
Sun Mar 30 20:08:51 2008: Starting socketmonitor threads
Sun Mar 30 20:08:51 2008: Connection closed
Sun Mar 30 20:08:52 2008: Stopping socketmonitor threads

P.P.S. The same problem appears to happen on Ktorrent 2.2.5 from openSUSE's "Packman" repository.

Sounds like you are just dropping connections to seeders, they are useless if you are also a seeder.

Thanks for the response. I'm the only seeder in this instance, so it can't be that. I see this problem with torrents that I create myself. Or, are we not on the same page?

Can you send me this torrent ? So I can try to connect to you.

OK, I'll set something up tomorrow.

I emailed you a torrent to test this out.

I tried using Transmission on the same PC that runs Ktorrent, and I had the same problem. So, it would seem that the problem is more general than I thought. In summary:

FreeBSD + Ktorrent on PC#1 = works
Suse + Ktorrent on PC#1 = doesn't work
Suse + Transmission on PC#1 = doesn't work
OSX + Transmission on Mac = works

Both the PC and the Mac are behind the same NAT firewall.

So, let's put this issue on the back burner for a while. It seems to be a problem with Suse.

Curiously, some peers can connect right through, but the majority can't.