Bittorrent Firewall issues

I'm getting firewalled at port 6881, anybody might know why and how to get around it?

I use the latest version of azureus.

Try 6881-6889.

Try 6881-6889.
What he said.
Manually configure your firewall to open these ports.
Another possibility would be to give azureus the full authorisation for out- and incoming connections (if you have the 'lite' version of some of the popular free firewalls).

I had major issues with a Zonealarm (free) and Azareus.

I've switched to Kerio and Shareaza, and it just flows. I did have to do some port forward work, Shareaza comes with an excellent how-to guide on that.

I had major issues with a Zonealarm (free) and Azareus.

I've switched to Kerio and Shareaza, and it just flows. I did have to do some port forward work, Shareaza comes with an excellent how-to guide on that.
Do you have the pro-version of Kerio or the free one?
I use the free lite-version and I never figured out where to do the port configuration.

do you have a router or switch. if so look on the companies website for configuring bit torrent for their equipment, i know dlink has specific instructions. as far as 68881 i know a lot of sites that block this port because everyone was using it and they suggest trying different ranges. here is some info that should help:

Why do I get a "rejected by tracker - Port xxxx is blacklisted" error?
Your client is reporting to the tracker that it uses one of the default bittorrent ports (6881-6889) or any other common p2p port for incoming connections. Torrent sites dont allow clients to use ports commonly associated with p2p protocols. The reason for this is that it is a common practice for ISPs to throttle those ports (that is, limit the bandwidth, hence the speed). The blocked ports list include, but is not neccessarily limited to, the following:

Direct Connect
411 - 413
Kazaa
1214
eDonkey
4662
Gnutella
6346 - 6347
BitTorrent
6881 - 6889

In order to use use some trackers you must configure your client to use any port range that does not contain those ports (a range within the region 49152 through 65535 is preferable, cf. IANA). Notice that some clients, like Azureus 2.0.7.0 or higher, use a single port for all torrents, while most others use one port per open torrent. The size of the range you choose should take this into account (typically less than 10 ports wide. There is no benefit whatsoever in choosing a wide range, and there are possible security implications).

These ports are used for connections between peers, not client to tracker. Therefore this change will not interfere with your ability to use other trackers (in fact it should increase your speed with torrents from any tracker, not just ours). Your client will also still be able to connect to peers that are using the standard ports. If your client does not allow custom ports to be used, you will have to switch to one that does.

Do not ask us, or in the forums, which ports you should choose. The more random the choice is the harder it will be for ISPs to catch on to us and start limiting speeds on the ports we use. If we simply define another range ISPs will start throttling that range also.

Finally, remember to forward the chosen ports in your router and/or open them in your firewall, should you have them. See the Why am I listed as not connectable? section and links therein for more information on this.

Do you have the pro-version of Kerio or the free one?
I use the free lite-version and I never figured out where to do the port configuration.

Free. Port config is done, for me, in my router (linksys). You just need to go to Kerio's applications list, and fiddle around with you p2p until it flows. But there might be a large number of bottlenecks, so it's hard to know when you've hit the sweet spot.