I tried to download Ubuntu (using SUSE 10.3, new download/install) but after downloading for quite a while I went to check on the progress. I had overlooked a small triangle in the lower left corner of the screen (Ktorrent) that said in essence "No information being stored (possible fire wall problem)
I went into yast and checked the eth cards being used. The wrong card had beem configured (eth1) I reconfigured to use eth0. However the situation persists.
Could this be a problem with the ports that are open? The initial torrent (instruction set) downloaded so why when I used KTorrent program did everything fail?
Any ideas or thoughts?

Forgot to mention, I don't have a router, so I really only need eth0 card.

A couple of questions that may help:

- What are your firewall settings?

- Is Comcast your ISP?

My isp is Verizon, I'll get you the settings, but I have to find them first.

There were settings on different pages (I went into YaST).

Can you tell me what you are looking for and I will write them out and report back?

In a console, as root, try iptables -L -n and see if that gets you the settings. If you need to you can redirect the output to a text file: iptables -L -n > file.txt and then file.txt will have the output.

Thank you Hangdog, I'll give it a go tomorrow and see if I can get it done.

Here it is Hangdog:
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
input_ext all -- 0.0.0.0/0 0.0.0.0/0
input_ext all -- 0.0.0.0/0 0.0.0.0/0
input_ext all -- 0.0.0.0/0 0.0.0.0/0
LOG all -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-IN-ILL-TARGET '
DROP all -- 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy DROP)
target prot opt source destination
LOG all -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-FWD-ILL-ROUTING '

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state NEW,RELATED,ESTABLISHED
LOG all -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-OUT-ERROR '

Chain forward_ext (0 references)
target prot opt source destination

Chain input_ext (3 references)
target prot opt source destination
DROP all -- 0.0.0.0/0 0.0.0.0/0 PKTTYPE = broadcast
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 4
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 8
LOG tcp -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 tcp dpt:22 flags:0x17/0x02 LOG flags 6 level 4 prefix `SFW2-INext-ACC-TCP '
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
reject_func tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:113 state NEW
LOG all -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 PKTTYPE = multicast LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT '
DROP all -- 0.0.0.0/0 0.0.0.0/0 PKTTYPE = multicast
LOG tcp -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 tcp flags:0x17/0x02 LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT '
LOG icmp -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT '
LOG udp -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT '
LOG all -- 0.0.0.0/0 0.0.0.0/0 limit: avg 3/min burst 5 state INVALID LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT-INV '
DROP all -- 0.0.0.0/0 0.0.0.0/0

Chain reject_func (1 references)
target prot opt source destination
REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 reject-with tcp-reset
REJECT udp -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-proto-unreachable

OK, that looks a bit odd, but if I'm reading it right, you don't really have a firewall. The first rule in each chain is to accept everything, which should mean that all packets are being passed without any issue. However, it is clear that there are a bunch of other rules there, and I'm not sure if they are being invoked.

I don't use Suse, so I'm not exactly sure how to do this, but I would try turning off your firewall completely and see if that makes a difference. There is probably a GUI tool in Yast to turn it off completely.

The other thing I would do would be to try to start a torrent from a different torrent server and see if you have any luck. It doesn't matter what you try and download (Knoppix, Slackware, or some other distro would be good) just something that will tell you if it is working or not.

What I'm trying to do is get some clues as to the actual culprit here. It could be your bittorrent client, your firewall, the torrent tracker or your ISP. I know you don't have Comcast, but I've never thought of Verizon as being any more virtuous than Comcast, so it could be they are also blocking bittorrent traffic and just haven't been caught yet. You also might read your bittorrent client documentation and see if there is a way to encrypt traffic. If Verizon is blocking torrents, encrypting the traffic may confuse them and allow it to proceed.

I had SUSE 10.2 installed. When 10.3 came out I downloaded (via Ktorrent) and installed it by "Updating", not a total new install. I had 3 directories "/", swap, /Home.
You say I don't have a firewall, thats just ducky!!

I am going to take one thing at a time. At this point I think "scatter hitting" solutions is going to get me into a deeper hole!

1. I'm going to get a working version of "Transmission" downloaded and working, I still think KTorrent has something to do ith the problems.

Problem being I am unsure of what I'm doing. We'll see.

Have you tried using another client? Like azureus?
Also, try using wireshark to see if the remote packets are even reaching you. I wouldn't be suprised if Verizon blocks all bittorrent traffic. If they are, I think you can set up bittorrent through a proxy or an anonymous network like The Onion Router and bypass their firewall.
Pirates don't give up. Be innovative!