Bitcomet Port Forwarding (TCP/UDP)

Bitcomet Port Forwarding (TCP/UDP) : -
Today, i've found this guide on how to do port forwarding on your bitcomet. No wonder i wasn't getting good speeds, it's bcoz i didn't get any remote connection.After i done this, my speed slightly increase, with remote type connection appearing over the peers of course. After that, i'd found another problem, ever since service pack 2 was introduced, they will only provide 10 tcp connection, and so, i have to edit it..again. And once again, thanks to this guide for showing me how.

Your download speed in BitTorrent/BitComet, or any other P2P (Peer-2-Peer) application for that matter, relies on the upload speed of others - so do not assume that because you get xxKB/s when downloading from web sites that you will always get xxKB/s with BitComet. Slow download speeds are almost always because the upload bandwidth required to provide you with fast downloads just isn't there¡K so there is no way to magically speed it up, other than going out and buying everyone who you're downloading from (seeds/peers) a faster internet connection.

With that said, if you do the following you should end up with around the best possible speeds:

1) Configure Port Forwarding

BitComet requires you to be able to receive incoming connections. If you're behind a NAT router (this does not apply to modems) but don't have port forwarding configured properly, incoming connections will be stopped by your router (won't reach your computer) and you'll end up with speeds of only a small percentage of what you're capable of getting. You need to configure port forwarding so your router knows that the incoming connections are for BitComet and will be allowed through (forwarded) to your computer.

An easy way to see if your port forwarding is configured properly or not is to see if you're receiving incoming connections to BitComet by doing the following test.

Start downloading a torrent that has lots of seeds/peers (like 100+), wait 5 minutes then look in the Peers section (bottom left of BitComet). Under the ¡yInitiation' column on the bottom pane, look to see if some peers are listed as Remote or if they're all Local. Make sure you scroll all the way down the list and look at all of them.

If you have a mix of Remote and Local like the picture above, it's a sign that your port forwarding is configured properly already (probably done automatically via UPnP) ¡X so skip to the next section.

Note: It doesn't matter how many Remote/Local connections you have, all that matters is you have both.

If you only have Local initiated connections (and possibly also NAT Traversal connections) like the picture above, it means incoming connections are most probably being stopped by your router or firewall, so you need to configure port forwarding.

To configure port forwarding, open up BitComet and go to Options > Preferences.

Here you need to enter a single ¡uListen Port¡v to be used for BitComet. It's best to use a listen port between 49152 and 65534 because they're classed as ¡uDynamic and/or Private Ports¡v by IANA, so nothing else should be using them by default and they're not the standard ones blocked by ISPs or trackers, but you can enter any other port you wish. It's strongly recommended that you don't use any between 1-5000, 6881-6999 or any listed on this page to avoid compatability problems. Again, it's best to choose a number between 49152 and 65534.

Write down your Listen Port number before clicking OK to exit out of BitComet's preferences. Next, in windows, click Start then Run Type cmd and press enter.

You should now be at a command prompt (a black box), so type "pconfig" and press enter. It should show you something similar to this:

「IP Address」 is your computers IP address that you need to forward the port to.

「Default Gateway」 should be your routers internal IP address.

Write down both of these numbers and then you can close the command prompt window.

Now you have all the information required to configure port forwarding in your router. But because there are so many routers and they're all different, I can't explain step-by-step how to configure port forwarding in your exact model. Hopefully you can find your router on this list and view step-by-step port forwarding instructions. If it's not there, look for some by the same manufacturer (because they'll probably be similar to yours), read your user guide or just start browsing through it's configuration sections - look for something along the lines of 「virtual server」, 「port mapping」 or 「port forwarding」. If you don't know the username and password for your router, check your user guide or see the default password list.

When configuring port forwarding in your router, you need to do the following… Log in to your router by entering the 「Default Gateway」 (the number you wrote down earlier from the ipconfig) into your web browser, like this:

Then navigate to the section for port forwarding and forward the 「Listen Port」 that you entered in BitComet's preferences to your computers 「IP Address」 for TCP & UDP. If it asks for a 』start port' and 『end port', enter your Listen Port in both. If it doesnt have an option for 「TCP & UDP」 together, first do port forwarding for TCP then repeat the process and choose UDP the second time. This is a lot simpler than it sounds, for example, a screenshot showing how I'd configure port forwarding in my router can be found here.

After you've done that, restart BitComet and try the test for Remote connections again. If you set up port forwarding correctly you should now be getting some Remote connections — along with greatly increased speeds.

NOTE: Another cause for a lack of incoming connections can be from an incorrectly configured transparent proxy (no configuration needed on the clients end) being run by your ISP which is not be sending your real IP address to trackers run on port 80. If this is the case, there isn't much you can do other than emailing your ISP and asking them configure the proxy to report your current IP address in HTTP_X_FORWARDED_FOR rather than the proxy's IP address. You can check proxy settings here (you may have a problem if doesn't display the IP address that your ISP has assigned you at the top of the page or as 「X-Forwarded-For」).

For these reasons, it's strongly recommended that you check for remote initiated connections with a torrent that uses a tracker on a port other than 80 (if it displays port 80 or no port at all in the tracker address then it uses port 80, so try a different one).

Forwarded From :

Destiny's Blog