Hi,
I had the problem of cox blocking bittorrent but I got around it by changing
my default port to a new number (something out side of the 6000 range)
I use azureus (http://sourceforge.net/projects/azureus/) as my client and used
the NAT tool to test ports tell I found one that worked.
--
Thank you,
[======================]
|Winter Faulk
|ph. 707.442.8393
|cell. 707.845.6411
|Winter@xxxxxxxxxxxxxxx
[======================]
On Friday 16 December 2005 22:03, Eric wrote:
Does anyone else have trouble using bittorrent with cable internet
access from Cox? I've been having issues with it since they replaced my
ancient cable modem, and I strongly suspect that Cox is actually zapping
my bittorrent connections by injecting RST packets into the TCP stream.
Tech support told me that they do not do this.
However, I know for a fact that Cox is blocking my attempts to connect
to my free email provider's smtp server (smtp.hotpop.com) on port 25 AND
that I became subject to this outbound connection filtering only after
they replaced my modem.
I could really use more data points on this, folks. If you're using Cox,
let me know if you can use bittorrent. If you're feeling extra nice, it
would be great if someone experiencing problems with bittorrent on Cox
could record some of the traffic with tcpdump and send me the capture
file. Messages over 300KB probably won't get through.
If you're willing to help out, the best thing to do would be to use a
bittorrent client other than BitComet and try to download the latest
debian DVD from
http://cdimage.debian.org/debian-cd/3.1_r0a/i386/bt-dvd/debian-31r0a-i386-bi
nary-1.iso.torrent I've definitely been having trouble with this one.
Thanks,
Eric
P.S.
I'm back to GPG signing my email. We'll see how long it lasts this
time. :/
--
Thank you,
[======================]
|Winter Faulk
|ph. 707.442.8393
|cell. 707.845.6411
|Winter@xxxxxxxxxxxxxxx
[======================]
|