yrana2002
01-12-2005, 03:55 AM
I dont know about other BT applications, but since i've been using bitcomet only, here's my guide:
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 'Initiation' 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, it's a sign that your port forwarding is configured properly already (probably done automatically via UPnP) -- 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) 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 "Listen Port" to be used for BitComet. It's best to use a listen port between 49152 and 65534 because they're classed as "Dynamic and/or Private Ports" 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, so type 'ipconfig' 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. Hopefully you can find your router on this (http://www.portforward.com/routers.htm)list and view step-by-step port forwarding instructions. For BSNL broadband users, the router will most likely be SMARTAX MT882. If you don't know the username and password for your router, check your user guide or see the default password list (http://www.phenoelit.de/dpl/dpl.html).
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.( 198.168.1.1)
Enter username & password as admin(default)
Go to NAT & enable NAT.
Then navigate to the section for Virtual Server 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.
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.
2) Allow BitComet access through any firewalls
Windows XP SP2 Firewall
Whenever 'Listen Port' is mentioned, it refers to the Listen Port you have chosen here in BitComet:
Options > Preferences > "Listen Port"
Go to Start > Settings > Control Panel > Network and Internet Connections > Network Connections.
Right click the Local Area Connection and choose Properties (if there is more than one use the one that says Connected underneath). Then click the Advanced tab.
Click the Settings button and go to the "Exceptions" tab. Click the Add Program button. Select BitComet then click OK.
A Simiar process can be adopted for various other firewalls.
3) Increase the number of connections BitComet can use
By default, BitComet allows very few peer connections per task. Although this may give slower speeds when you first install BitComet, the stability is increased, which is probably the best way to release a software like this. After people have it installed an running stable, they can start to tinker.
A good deal of extra speed can usually be gained by simply increasing the following:
Options > Preferences > Advanced > Connection > "Maximum Connections per task"
Options > Preferences > Advanced > Connection > "Connections to keep per task"
Please note that more isn't always better and setting these values too high could give you slower speeds and/or make your modem/router disconnect. For example, some people will tell you to set the "Maximum Connections per task" to 1000... while it might work great for them, it could have a negative effect on your setup.
5) Select a Fast Tracker
Public trackers usually give poor speeds compared to Private trackers, but they have more content. Public trackers can be used by anyone and there are rarely any penalties towards those who choose not to upload, so they generally give slower speeds. Private trackers require (free) membership and members must maintain a certain download:upload ratio, so there are a lot more people uploading ('seeding') and downloads are much faster.
If you want faster download speeds, try using a private tracker that has a better seed to peer ratio (more people uploading).
Did i mention that you have to maintain a good upload ratio & even seed dead torrents to keep connection with the tracker. Or else, you're likely to be kicked outta there.
A list to best private trackers (http://www.orbdesign.net/bt/)
Courtesy----
Dragosani.
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 'Initiation' 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, it's a sign that your port forwarding is configured properly already (probably done automatically via UPnP) -- 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) 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 "Listen Port" to be used for BitComet. It's best to use a listen port between 49152 and 65534 because they're classed as "Dynamic and/or Private Ports" 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, so type 'ipconfig' 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. Hopefully you can find your router on this (http://www.portforward.com/routers.htm)list and view step-by-step port forwarding instructions. For BSNL broadband users, the router will most likely be SMARTAX MT882. If you don't know the username and password for your router, check your user guide or see the default password list (http://www.phenoelit.de/dpl/dpl.html).
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.( 198.168.1.1)
Enter username & password as admin(default)
Go to NAT & enable NAT.
Then navigate to the section for Virtual Server 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.
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.
2) Allow BitComet access through any firewalls
Windows XP SP2 Firewall
Whenever 'Listen Port' is mentioned, it refers to the Listen Port you have chosen here in BitComet:
Options > Preferences > "Listen Port"
Go to Start > Settings > Control Panel > Network and Internet Connections > Network Connections.
Right click the Local Area Connection and choose Properties (if there is more than one use the one that says Connected underneath). Then click the Advanced tab.
Click the Settings button and go to the "Exceptions" tab. Click the Add Program button. Select BitComet then click OK.
A Simiar process can be adopted for various other firewalls.
3) Increase the number of connections BitComet can use
By default, BitComet allows very few peer connections per task. Although this may give slower speeds when you first install BitComet, the stability is increased, which is probably the best way to release a software like this. After people have it installed an running stable, they can start to tinker.
A good deal of extra speed can usually be gained by simply increasing the following:
Options > Preferences > Advanced > Connection > "Maximum Connections per task"
Options > Preferences > Advanced > Connection > "Connections to keep per task"
Please note that more isn't always better and setting these values too high could give you slower speeds and/or make your modem/router disconnect. For example, some people will tell you to set the "Maximum Connections per task" to 1000... while it might work great for them, it could have a negative effect on your setup.
5) Select a Fast Tracker
Public trackers usually give poor speeds compared to Private trackers, but they have more content. Public trackers can be used by anyone and there are rarely any penalties towards those who choose not to upload, so they generally give slower speeds. Private trackers require (free) membership and members must maintain a certain download:upload ratio, so there are a lot more people uploading ('seeding') and downloads are much faster.
If you want faster download speeds, try using a private tracker that has a better seed to peer ratio (more people uploading).
Did i mention that you have to maintain a good upload ratio & even seed dead torrents to keep connection with the tracker. Or else, you're likely to be kicked outta there.
A list to best private trackers (http://www.orbdesign.net/bt/)
Courtesy----
Dragosani.