Port issue with bitcomet
Solved
Kanon42
-
Cosss -
Cosss -
Hello,
I have a firewall problem with BitComet; all of a sudden, the connection is blocked by the Livebox, which changed my IP address.
So I reconfigured it for Emule and BitComet, and the result is Emule works fine, but BitComet is blocked by some unknown issue???
Windows Live Firewall is open and the Sagem Livebox port is open.
If anyone can help me.
Thanks in advance
Best regards
Kanon 42
I have a firewall problem with BitComet; all of a sudden, the connection is blocked by the Livebox, which changed my IP address.
So I reconfigured it for Emule and BitComet, and the result is Emule works fine, but BitComet is blocked by some unknown issue???
Windows Live Firewall is open and the Sagem Livebox port is open.
If anyone can help me.
Thanks in advance
Best regards
Kanon 42
Configuration: Windows XP Firefox 2.0.0.9
13 answers
-
Having had the same problem with that infamous yellow point on BitComet and after struggling, I finally succeeded, so I hope this can help. Please note that I am using a Netgear modem from Numericable on Windows XP. First of all, to answer a question posed earlier, BitComet 1.09 works very well with very simple settings and good upload speed. For the yellow point, I went to Google and typed in the address bar (only in the bar) 192.168.0.1, then entered admin and password. There you are in your modem. In the configuration, go to UPnP and enable it. Then for DMZ host, enter the last two digits of your IP address in the DMZ address box (default is 0) and apply. Launch your BitComet and there you go, magic. Please know that I am a novice but stubborn lol, so if you have any further questions or disputes, feel free to contact me.
-
-
If some still haven't understood, to have the little green circle at the bottom, you need to open the ports used by BitComet in your firewall and on your router. For the Windows firewall, you just need to add exceptions for UDP and TCP (firewall > exceptions > add a port). Do the same on your router; for that, you need to type in your router's IP address, often 192.168.0.1 or 192.168.1.1, something like that. Go into the settings and under NAT, create two entries with the port used by BitComet in both UDP AND TCP. For me, with my Club-Internet modem and using port 23391, it would be:
BitComet Server Name / BitComet
External Start Port: 23391 / 23391
External End Port: 23391 / 23391
Protocol: TCP / UDP
Internal Start Port: 23391 / 23391
Internal End Port: 23391 / 23391
Server IP Address: 192.168.1.2 / 192.168.1.2 (your local IP address)
End, well I know that by doing this it worked for me; before, I never exceeded 20 KB/s, now I never drop below 200 KB/s, often a minimum of 150 KB/s. -
-
-
-
-
-
Issue resolved
By changing the port from 6881 to a port higher than 15000 (random port case)
Thanks anyway -
I can access http://192.168.1.1 but it asks me for a username and a password that I don't know!! Can someone help me?!
-
Configure <livebox> for BITCOMET (Blocking the Listening Port)
Go to the config with URL: 192.168.11
Password "admin"
Go to "Advanced Configuration."
- Note the port number indicated in "Options" of the BitComet application,
- in "application service" look for <new> and indicate Bitcomet.
- Then, indicate the port number used by BitComet and in "protocol," indicate <both>.
- In "device," take the name of the PC used (usually, it appears alone).
- Validate and it's OK. The <wan> indicator turns green on the BitComet window.</wan></both></new></livebox> -
-
A bump because I had the same issue with the blocked port problem but with the Livebox 2
The solution from Apnea works perfectly Thank you -
Which version of BitComet works best without any modifications?
-
Which version of BitComet works best without any tweaks because version 1.09 doesn't work well?
-
Hi
how do you find the ports used by BitComet..??
I don’t see anything in the "options" tab??
thanks -
I have the same problem, but I don't have a router; I have an ADSL modem, and I can't do the trick?
-
Thank you Polo, it works for me. My IP address when I was configuring NAT was that of my gateway, that's why it didn't work. So one piece of advice, use your real IP address for it to work.
-