Comment ouvrir un port d'écoute sur le routeur pour BitComet
deuff80
-
MélaniePP -
MélaniePP -
Hello,
I have a problem with Bit Comet because I'm downloading slowly (max 50kb/s). In fact, I have a yellow dot at the bottom right indicating that my listening port is blocked by a firewall or NAT router configuration. I have Bit Comet 1.07 and my router is a Hercules 802.11 g. Would there be a kind soul on this icy Sunday to give me the steps to follow so that I can download at high speed, please, and watch a nice little movie all warm? Thank you in advance.;-)
I have a problem with Bit Comet because I'm downloading slowly (max 50kb/s). In fact, I have a yellow dot at the bottom right indicating that my listening port is blocked by a firewall or NAT router configuration. I have Bit Comet 1.07 and my router is a Hercules 802.11 g. Would there be a kind soul on this icy Sunday to give me the steps to follow so that I can download at high speed, please, and watch a nice little movie all warm? Thank you in advance.;-)
Configuration: Windows XP Firefox 3.0.5
8 answers
-
You just have to reset your router, then close BitComet and turn it back on. It worked for me.
-
-
Hi,
Use µtorrent, much fewer problems with it....
Anyway, it's just a suggestion :) -
-
-
I'm going to explain this to you, because I had the same problem. So you have an IP (192.168.1.1 for Orange/Livebox): you type http://192.168.1.1 in your browser (http://l'ip which corresponds to your provider). It will then ask you for a login and a password: admin for the login and admin for the password. You will then arrive on a page that says LAN SERVER: click on it. Scroll all the way down the page and there it says public port: remember this. Click on new entry (above what I asked you to look at) and there you enter the following things:
server name: bitcomet
access enabled: yes
from port: here you enter the one I asked you to remember
to port: here you enter the one I asked you to remember
protocol: TCP
local IP address: 192.168.1.10 (if you are with Orange)
Then, you repeat this process a second time, but instead of putting TCP as the protocol, you put UDP:
server name: bitcomet
access enabled: yes
from port: here you enter the one I asked you to remember
to port: here you enter the one I asked you to remember
protocol: UDP
local IP address: 192.168.1.10 (if you are with Orange)
there you go! You start bitcomet (or restart it if it was already running) and voila! It works ;) -
I will explain this to you because I've had the same problem. So you have an IP (192.168.1.1 for Orange/Livebox): you type http://192.168.1.1 in your internet browser (http://l'ip which corresponds to your provider). It will then ask you for a login and a password: admin for the login and admin for the password. You will then arrive at a page where it says LAN SERVER: click on it. Scroll all the way down the page and there you will see public port: remember that. Click on new entry (above what I asked you to look at) and there you enter the following things:
server name: bitcomet
access enabled: yes
from port: here you enter the port I asked you to remember
to port: here you enter the port I asked you to remember
protocol: TCP
local IP address: 192.168.1.10 (if you are with Orange)
Now, you do this manipulation a second time, but instead of putting TCP as the protocol, you put UDP:
server name: bitcomet
access enabled: yes
from port: here you enter the port I asked you to remember
to port: here you enter the port I asked you to remember
protocol: UDP
local IP address: 192.168.1.10 (if you are with Orange)
There you go! You start BitComet (or restart it if it was already running) and tadaa! It works ;) -
I'm going to tell you why it's blocking. It's because providers systematically block the ports you use with your peer-to-peer software like eMule, for example. They have routers that listen to the used ports, and as soon as they detect peer-to-peer traffic, they limit the bandwidth. Initially, it was only with unbundled subscribers, but now everyone is affected. In conclusion, you need to change your ports regularly. Unfortunately, in this game of hide and seek, we will soon have no free ports left. Especially since providers don't just block the port you've used, but also a few before and after the port you've used. For example: on day J, I use port 40032, which works perfectly fine. A few days later, bam... port blocked. Don't try port 40033, it will be blocked, just like thousands in that range. The internet will soon be completely locked down, and you won't have much room for maneuver left! Long live the NWO !!