If port 6969 has to be forwarded for BT, then how come the NAT wizard 
doesn't include a rule for it?  Besides that, how is it possible that I'm 
running more-or-less OK now without that port?

NHA
---
Norman H. Azadian    Taegerishalde 13    CH-3110 Muensingen    Switzerland
norman at azadian dot ch      tel: +41 31 721 7855      fax: +41 31 55 898 55


Mark Hesseltine wrote:
> Norman H. Azadian wrote:
> 
>> I used the NAT wizard for Bit Torrent, then I went in and changed the 
>> default port range 6881-6889 to port 49999 that I've configured 
>> azureus for.  Now I'm finding that seeds are almost always blue 
>> instead of green. I'm not certain it's the firewall, but it does look 
>> like it.  Any ideas?
>>
>> NHA
> 
> 
> While your incoming BitTorrent packets will come in on port 49999, you 
> also need to make a connection to the tracker. Most trackers run on TCP 
> port 6969, but you will find occasional trackers that run on oddball 
> ports as well. That may be your problem. I've run into that running a 
> Linux based firewall at home, and had to occasionally open a port to 
> connect to one oddball tracker, then close the hole when I was done with 
> that download.
>