Can`t get connectable!!, page 1

Please forgive me but I´m going crazy to try to be connectable. Is there someone to tell me in detail for dummies what ports are important to get it made?
The following steps I made but no success:
1)I have a router (fritzbox sl - a german product) and opened port 6969 as tcp for the tracker. Is that right?
2)I`m using ABC 3.0 and opened the ports there above the 40000? OK?
3)And I´m using a firewall and opened:  tcp in/out port 6969 for the local endpoint (this is me right?) for the tracker and for tcp out there are all ports allowed and it uses the ports from 2)

Connecting out is no problem but connecting in is the question. I don`t want to open to much ports for others, so I don`t need a firewall!

What the hell I´m doing wrong or what`s missing? Please help and please don`t tell me "read the faq or the portforwarding" stuff. I made that and no help in there.

Please don`t be annoyed (Sysops, Admins, Mods) and help me. PLEASE!!!

1. the thing is, tracker doesn't use port 6969. it uses regular port 80 for tcp connections, and this port is already configured pretty much in your firewall and router. i think. so basically you don't need to think about opening ports for tracker, on top of that it doesn't have anything to do with being connectable.

2. second step of yours was right. it's very important to use ports over like 40000. say i found a little range - 48990-48999 which usually are connectable 99% of the time. works for me, at least.

3. that port range you chose, that is the range you MUST open in your ROUTER and FIREWALL. so what you have now is good, but it's not written in firewall, so you need to do it.

4. what is the best to do... open special range of ports in router (haven't used one in 2 years, so i don't really remember all that stuff, but routers differ much, so it wouldn't help), write them in ABC and allow all kinds of incoming and outgoing connections on all ports for ABC in your firewall. this will not affect your security, because router already works for it. usually double firewall (router+software) only slows down much all kinds of communication, especially torrent p2p commn.

all right, hope it all helps. you can also use those links in faq on ports, and check the ports you wanna use there, it will show if you are connectable on those ports.

ahh thanks. slash. First time someone answers my question really and in detail. You are awesome. Thanks.

hey, this is all good. tell me if it helps. everybody's situation is different from others, so there are different ways of fixing all the holes.

and don't forget the usual and well known procedure: if your peers show as unconnectable, try
 - changing port to a pretty different number
 - restarting client or torrents in client
helps me usually on 3-5th restart.

IF you have any issues setting up any router check out https://www.portforward.com/routers.htm

Unfortunately, I am still partially not connectable. I recently moved and am not currently using a router. Time to play around and get mine to work as well

.....3 hours later.........
OK still having issues.

Since I am not using a router, I told my firewall to allow port 80 to go to my bitclient. Dont think I should add any other ports to it? I cant specify a range on the firewall, any suggestions??

Thanks, Daddycogg

(Maybe I should just hook my router back up, its already configured)

it is not port 80 that allows communication of tracker and client at your computer. for explorer - yes, not for torrent client. your client is using some different port, which is listed in its config window. look it up there and open it in firewall. it will be easy for azureus cause it's only using 1 port for all downloads.

when trying to work out the problem don't forget to restart torrents or client. that is because when you staeted it and some or all peers came up not connectable, there's a big chance that port they tried to use is highly clogged up, so you should change it and rerun the client. that is how i do it. and on top of that i have all ports accessible by azureus, so that i don't have to work with firewall everytime i change port. bacause it is only for client, i can do that, cause any other (like virus or attack) comminication will not go to azuereus, hence it will be blocked by firewall.

AfI now have all of my ports forwarded to the correct places, and at first was still having issues with some of my connections.

Finally I figured out the problem.(wasn't actually the ports! The configuration I had with my router should have been fine)  I have "disconnect from seeds when seeding" checked in Azureus. IS it ok for me not to be connected to other seeders? I would think that it would be fine.

If I need to stay connected to other seeders let me know!!!!


Thanks for all the help

no, it's not important if other peers are connectable. this feature is for seeds to act in connection as to give different peers different portions of file, so that when all seeds together have uploaded just 1 copy (every seed less than a copy) - all peers together will have 1 copy too (each peer got something from seeds and shared it with others. it's possible that no peer would already have full copy but now peers are set to share between them and get file even without seeds. that is the very core of bittorrent structure of traffic. but we don't have too many connectable peers, so it is not a big deal.

NOT connectable peers: 2
why unconnectable them?
i am using peer guardian and azureus's safe peers plugin.
unconnectable is for them?
i am not blocking anything for myself.

I figured it out finally. I had to hurry up, because I´m warned of my ratio. So I uploaded 1 set. Finally I´m connectable with my upload. But another seed which I`m supporting is not connectable. Why? Please help quickly.