Topic: help with BT firewall?

[kkaye]

Can someone help me figure out how to forward the ports on my Verizon DSL connection?

Im looking on this page:
http://knowbuddy.dyndns.org:81/torrent/btclientconfig.html

I have a Westell Wirespeed A90.
Im trying to follow those directions but its not working.

Can anyone help

[Brian Skalinder]

With what exactly are you having trouble?

[Sean Gallemore]

Are you using a router?

[Joe w.]

the Westell Wirespeed A90 is the router.

[phishn]

are you running windows XP as well?  If so, make sure the ethernet connection to your router is not firewalled.  XP has a software firewall built in which serves no purpose if you are using a hardware firewall/router.  You may be double firewalled.

[momule]

Depending upon your network configuration, it may not be enough just
to open up those ports.  You may have to forward them as well.

If you use a computer on a home network, and your Internet connection
is through a NAT (Network Address Translation) gateway, you may have
to tell that NAT gateway to forward all incoming traffic in the
BitTorrent port range to the internal PC on which you run the
BitTorrent downloader.

(If more than one computer in your house is able to connect to the
Internet at the same time, you are almost certainly doing so via a NAT
gateway.)

Your cable/DSL router probably supports NAT.  So why do you need to
enable port forwarding?  Simple: because all the internal machines
"hide" behind one external IP address, the NAT gateway machine needs
to be told *for incoming connections* which of the possible internal
machines should receive that traffic.  (For outgoing traffic, it can
route returning packets because it remembered from which internal
machine they originated.)  Without port forwarding, the gateway
doesn't know where to send the incoming connection.  So, even though
you've opened up those ports on your internal PC (and perhaps even on
your external gateway), they never get forwarded to the right place.
Hence you appear to be "firewalled."

I can't tell you how to enable port forwarding on your setup, because
it depends upon your setup (equipment and topology).  I'm presuming
the admin interface of your Internet gateway box will have an option
for forwarding.  You should tell it to forward TCP ports 6881-6889
(default BitTorrent downloader port range) to the IP address of the
system on which you run the BitTorrent downloader (which is likely to
be a private address akin to 192.168.x.x).

(There's also always the possibility that your ISP filters out
incoming "BitTorrent traffic" as part of a blanket ban on serving,
e.g., via an upstream stateful packet filter.)

[Joe w.]

i dunno how it works on your particular router, but I have to login to my router at work through the default gateway address, which is usually similar on most networks....ex - 192.168.x.y, where x=same number on all systems and y=different/unique number on all systems on the network.

after i login as the admin, i can forward ports by choosing the port range and telling info to flow through those ports from the main ip addy.

[Sean Gallemore]

that's how my old router worked, joe

I don't know about the westell, though.

[Joe w.]

XP has a software firewall built in which serves no purpose if you are using a hardware firewall/router.  You may be double firewalled

Excellent point. If you wanna fix that, or turn it off:

http://www.microsoft.com/windowsxp/pro/using/howto/networking/icf.asp

[Idle Wind]

(There's also always the possibility that your ISP filters out
incoming "BitTorrent traffic" as part of a blanket ban on serving,
e.g., via an upstream stateful packet filter.)

I got Verizon business DSL at work not too long ago, but can't get BT to work at all.  I have only one
computer at work, running XP / SP2, connected by ethernet to a Westell 2200 connected to the phone
line.  Dell Dimension 2400.

I have Verizon home DSL service right down the street, same modem, Windows 98 SE2, and
it works fine.  I opened the firewall no problem.  I later put a linksys wireless, opened those
ports, no problem.

I can see the torrents, the file names end up on my HD, but no data, no download.  I get a
10060 "can't connect" error.  I disabled my XP firewall (the Westell one is still up,
with 6881-6889 open).  I tried Bittornado and BitComet.  same results.  can't connect to
the tracker, no matter how long I wait.  bt.etree.org torrents which have seeders/leechers.

SmartFTP's from llama work fine.

I'm completely at a loss.  Could Verizon be blocking it on the business line and not the home
line right down the street?

[chase]

instructions for forwarding ports for Westell routers

http://portforward.com/routers.htm



quick link to Westell 2200

http://portforward.com/westell/2200-portforwarding.htm



remember you need to find out which IP address your computer has.  you can find this by going to Start > Run > type in "cmd"

at the prompt type "ipconfig"

then in the settings of your router, forward ports 6881-6889 to 192.168.1.x    x = value for your address, most likely between 1 and 50.

[Idle Wind]

thanks.  +T.

I had my ports all forwarded correctly for TCP.  I did it for UCP as well.
I set my static NAT as the IP addy for my NIC - 192.168.1.47.
I had done all this on a Win 98 machine which works, and it's pretty
similar.

still no download or up load on my XP machine.
Error 10060 - can't connect to tracker.

BitComet sees the file set, has the details, but
can't DL any of it. "Connecting to Tracker - Waiting
for Reply to Say Start"....

I think its either an XP issue or a business DSL service issue
cause it works at home on 98SE

thanks though..

[chase]

I think its either an XP issue or a business DSL service issue
cause it works at home on 98SE

thanks though..

it is most likely your company's firewall blocking connections on the necessary ports, or blocking BT through a packet manager.

[Idle Wind]

I am the company.  ;-)  I disabled the windows firewall too - so it's
just the Westell, with 6881-6889 open.

I thought you could BT even with a firewall - just not well.
I can't at all.  So either I'm missing something, or Verizon is
blocking me.