Jump to content
Comet Forums
MrYumYum

new router, bitcomet cant listen to ports

Recommended Posts

P.S klulos, what do "Voici, l'erreur" and "Voici, l'erreur disparaƮt" mean??

It's French.

"Voici, l'erreur" means in approximate translation "here is the error" or "behold, the error" or "here you can see the error" and

"Voici, l'erreur disparaƮt" means "here you go, the error disappears" or "behold, the error disappears".

Share this post


Link to post
Share on other sites

bump

mm sorry to bring this up again as this error still exists

just letting you guys know i am now using a new ISP (adsl instead of cables)

ive also noticed im unable to fully reach the limits of my bandwidth (after adding several downloads with many seeds - most i could get is like a third out of what i could get with my old router)

am using version 1.25 now (latest one)

a wierd thing i noticed after changing my bitcomet's listening port is that the tcp port it's trying to connect is shown as 0 instead of the one i picked (unlike the udp port)

65429241.jpg

Uploaded with ImageShack.us

is this normal?

Edited by MrYumYum (see edit history)

Share this post


Link to post
Share on other sites

Switching to an Adsl ISP means you now have an adsl modem, what model? You might need to open/forward ports in the new hardware as well.

PS,

netstat -o -an |find /i "listening"
netstat -b -an |find /i "listening"

Shows what processes are listening to which ports. -o for PID and -b for Process name, you can combine them too.

Share this post


Link to post
Share on other sites

[bitComet.exe]

TCP 192.168.0.199:50039 98.156.125.201:53280 FIN_WAIT_1

[bitComet.exe]

TCP 192.168.0.199:50039 98.157.83.192:56737 FIN_WAIT_1

[bitComet.exe]

TCP 192.168.0.199:50039 98.197.51.53:2106 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 99.18.0.114:52791 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 99.38.32.176:61207 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 99.52.101.183:61216 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 99.71.237.112:60829 TIME_WAIT

TCP 192.168.0.199:50039 99.192.25.232:49357 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 99.240.221.43:53143 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 108.5.81.60:3656 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 108.66.14.22:61633 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 109.60.78.212:50477 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 109.76.165.95:1630 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 109.78.61.128:22264 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 109.92.240.207:4786 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 109.93.115.43:58246 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 109.200.0.44:65245 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 109.242.78.62:52569 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 110.3.71.210:4915 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 110.32.248.159:61875 LAST_ACK

[bitComet.exe]

TCP 192.168.0.199:50039 110.55.165.2:52401 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 112.198.64.29:44152 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 112.210.219.98:3614 TIME_WAIT

TCP 192.168.0.199:50039 114.79.41.233:49782 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 115.134.71.154:28496 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 115.134.187.147:55534 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 117.199.139.213:3607 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 118.100.165.5:1790 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 119.74.139.176:2278 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 119.154.121.170:1768 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 120.17.116.28:52390 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 120.140.225.21:51773 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 121.54.54.56:5743 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 121.82.131.205:49731 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 122.24.116.38:53268 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 122.167.137.149:52481 TIME_WAIT

TCP 192.168.0.199:50039 122.180.106.42:3076 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 124.106.237.160:55883 LAST_ACK

[bitComet.exe]

TCP 192.168.0.199:50039 124.106.237.160:56046 LAST_ACK

[bitComet.exe]

TCP 192.168.0.199:50039 124.122.182.202:26837 LAST_ACK

[bitComet.exe]

TCP 192.168.0.199:50039 124.187.19.198:60376 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 124.212.215.221:3948 TIME_WAIT

TCP 192.168.0.199:50039 124.247.207.228:1105 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 125.60.229.56:4211 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 131.191.48.134:3115 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 157.157.170.155:50606 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 173.67.32.162:64502 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 173.218.241.19:59687 FIN_WAIT_1

[bitComet.exe]

TCP 192.168.0.199:50039 175.104.20.208:21974 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 175.139.29.227:56628 FIN_WAIT_2

[bitComet.exe]

TCP 192.168.0.199:50039 175.139.29.227:56666 TIME_WAIT

TCP 192.168.0.199:50039 178.59.168.143:64193 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 178.74.82.163:34819 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 178.203.248.128:59024 FIN_WAIT_1

[bitComet.exe]

TCP 192.168.0.199:50039 178.203.248.128:59258 FIN_WAIT_2

[bitComet.exe]

TCP 192.168.0.199:50039 188.220.74.119:49182 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 188.223.114.33:62405 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 190.88.99.110:4671 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 198.37.17.131:64057 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 202.172.115.6:63771 TIME_WAIT

TCP 192.168.0.199:50039 205.206.252.97:58876 TIME_WAIT

TCP 192.168.0.199:50039 206.47.38.192:53853 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 206.163.253.107:1043 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 211.31.102.142:49603 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 211.108.38.10:1972 LAST_ACK

[bitComet.exe]

TCP 192.168.0.199:50039 211.108.38.10:2099 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 212.253.167.194:58503 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 213.25.140.128:1538 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 217.225.168.242:1335 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 218.212.58.178:63811 FIN_WAIT_1

[bitComet.exe]

TCP 192.168.0.199:50039 218.212.58.178:64234 ESTABLISHED

[bitComet.exe]

TCP 192.168.0.199:50039 222.127.241.172:54639 FIN_WAIT_1

[bitComet.exe]

TCP 192.168.0.199:50039 222.164.97.162:1918 FIN_WAIT_1

[bitComet.exe]

TCP 192.168.0.199:50039 222.165.124.212:62199 LAST_ACK

[bitComet.exe]

TCP [::]:135 [::]:0 LISTENING

RpcSs

[svchost.exe]

TCP [::]:445 [::]:0 LISTENING

Can not obtain ownership information

TCP [::]:554 [::]:0 LISTENING

[wmpnetwk.exe]

TCP [::]:1025 [::]:0 LISTENING

[wininit.exe]

TCP [::]:1026 [::]:0 LISTENING

eventlog

[svchost.exe]

TCP [::]:1027 [::]:0 LISTENING

Schedule

[svchost.exe]

TCP [::]:1028 [::]:0 LISTENING

[spoolsv.exe]

TCP [::]:1029 [::]:0 LISTENING

[lsass.exe]

TCP [::]:1033 [::]:0 LISTENING

[services.exe]

TCP [::]:1035 [::]:0 LISTENING

PolicyAgent

[svchost.exe]

TCP [::]:2869 [::]:0 LISTENING

Can not obtain ownership information

TCP [::]:3587 [::]:0 LISTENING

p2pimsvc

[svchost.exe]

TCP [::]:5357 [::]:0 LISTENING

Can not obtain ownership information

TCP [::]:10243 [::]:0 LISTENING

Can not obtain ownership information

UDP 0.0.0.0:500 *:*

IKEEXT

[svchost.exe]

UDP 0.0.0.0:3702 *:*

EventSystem

[svchost.exe]

UDP 0.0.0.0:3702 *:*

FDResPub

[svchost.exe]

UDP 0.0.0.0:3702 *:*

EventSystem

[svchost.exe]

UDP 0.0.0.0:3702 *:*

FDResPub

[svchost.exe]

UDP 0.0.0.0:4500 *:*

IKEEXT

[svchost.exe]

UDP 0.0.0.0:5004 *:*

[wmpnetwk.exe]

UDP 0.0.0.0:5005 *:*

[wmpnetwk.exe]

UDP 0.0.0.0:5355 *:*

Dnscache

[svchost.exe]

UDP 0.0.0.0:50023 *:*

[bitComet.exe]

UDP 0.0.0.0:54903 *:*

[mDNSResponder.exe]

UDP 0.0.0.0:61162 *:*

FDResPub

[svchost.exe]

UDP 0.0.0.0:61164 *:*

EventSystem

[svchost.exe]

UDP 0.0.0.0:62248 *:*

EventSystem

[svchost.exe]

UDP 127.0.0.1:1900 *:*

SSDPSRV

[svchost.exe]

UDP 127.0.0.1:51073 *:*

[bitComet.exe]

UDP 127.0.0.1:54901 *:*

[AppleMobileDeviceService.exe]

UDP 127.0.0.1:54902 *:*

[AppleMobileDeviceService.exe]

UDP 127.0.0.1:58192 *:*

[babylon.exe]

UDP 127.0.0.1:61160 *:*

[iTunesHelper.exe]

UDP 127.0.0.1:61161 *:*

[iTunesHelper.exe]

UDP 127.0.0.1:61169 *:*

SSDPSRV

[svchost.exe]

UDP 192.168.0.199:137 *:*

Can not obtain ownership information

UDP 192.168.0.199:138 *:*

Can not obtain ownership information

UDP 192.168.0.199:1900 *:*

SSDPSRV

[svchost.exe]

UDP 192.168.0.199:5353 *:*

[mDNSResponder.exe]

UDP 192.168.0.199:61168 *:*

SSDPSRV

[svchost.exe]

UDP [::]:500 *:*

IKEEXT

[svchost.exe]

UDP [::]:3540 *:*

p2pimsvc

[svchost.exe]

UDP [::]:3702 *:*

FDResPub

[svchost.exe]

UDP [::]:3702 *:*

FDResPub

[svchost.exe]

UDP [::]:3702 *:*

EventSystem

[svchost.exe]

UDP [::]:3702 *:*

EventSystem

[svchost.exe]

UDP [::]:4500 *:*

IKEEXT

[svchost.exe]

UDP [::]:5004 *:*

[wmpnetwk.exe]

UDP [::]:5005 *:*

[wmpnetwk.exe]

UDP [::]:5355 *:*

Dnscache

[svchost.exe]

UDP [::]:54904 *:*

[mDNSResponder.exe]

UDP [::]:61163 *:*

FDResPub

[svchost.exe]

UDP [::]:61165 *:*

EventSystem

[svchost.exe]

UDP [::]:62249 *:*

EventSystem

[svchost.exe]

UDP [::1]:1900 *:*

SSDPSRV

[svchost.exe]

UDP [::1]:5353 *:*

[mDNSResponder.exe]

UDP [::1]:61167 *:*

SSDPSRV

[svchost.exe]

UDP [fe80::109d:d836:e8d6:64ae%11]:1900 *:*

SSDPSRV

[svchost.exe]

UDP [fe80::109d:d836:e8d6:64ae%11]:61166 *:*

SSDPSRV

[svchost.exe]

heres what i get after typing: netstat -b -an

bitcomet shows yellow light

Share this post


Link to post
Share on other sites

You need to type the whole line netstat -o -an |find /i "listening" and then look at the rightmost column to see the process identifiers of each process listening on those ports. Then go to Task manager, in the processes tab, and order all processes after(click on the header of...) the PID column(go to view/select columns if the PID column is not shown).

Share this post


Link to post
Share on other sites

sorry about that =]

task manager shows my Bitcomet's PID (5356),

heres what cmd shows after typing: netstat -o -an |find /i "listening"

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 956

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4

TCP 0.0.0.0:554 0.0.0.0:0 LISTENING 4172

TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING 816

TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 1084

TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 1148

TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING 1592

TCP 0.0.0.0:1029 0.0.0.0:0 LISTENING 896

TCP 0.0.0.0:1033 0.0.0.0:0 LISTENING 880

TCP 0.0.0.0:1035 0.0.0.0:0 LISTENING 1248

TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING 4

TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4

TCP 0.0.0.0:10243 0.0.0.0:0 LISTENING 4

TCP 0.0.0.0:23166 0.0.0.0:0 LISTENING 5356

TCP 0.0.0.0:50027 0.0.0.0:0 LISTENING 2592

TCP 0.0.0.0:50039 0.0.0.0:0 LISTENING 5356

TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING 2040

TCP 127.0.0.1:10000 0.0.0.0:0 LISTENING 2592

TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING 1800

TCP 192.168.0.199:139 0.0.0.0:0 LISTENING 4

TCP [::]:135 [::]:0 LISTENING 956

TCP [::]:445 [::]:0 LISTENING 4

TCP [::]:554 [::]:0 LISTENING 4172

TCP [::]:1025 [::]:0 LISTENING 816

TCP [::]:1026 [::]:0 LISTENING 1084

TCP [::]:1027 [::]:0 LISTENING 1148

TCP [::]:1028 [::]:0 LISTENING 1592

TCP [::]:1029 [::]:0 LISTENING 896

TCP [::]:1033 [::]:0 LISTENING 880

TCP [::]:1035 [::]:0 LISTENING 1248

TCP [::]:2869 [::]:0 LISTENING 4

TCP [::]:3587 [::]:0 LISTENING 5104

TCP [::]:5357 [::]:0 LISTENING 4

TCP [::]:10243 [::]:0 LISTENING 4

Share this post


Link to post
Share on other sites

Y'know, you seem to have lost the plot here. WE don't need to know this and, since we're not at your console, it doesn't do us much good.

YOU need to know this, and by following Vasy's instructions, you can determine whether or not your BitComet process is actually listening at the correct port. So the only useful lines out of that last list are the ones that BitComet is using. Unfortunately, since we're not at your console, we can't determine what BitComet's PID is -- only you can do that.

Once you do that, you can do the rest of it. Is BItComet actually listening at the TCP port in question?

Share this post


Link to post
Share on other sites

You know, to make it simpler for you, after you've typed

netstat -aon|find /i "listening"

and retrieved the PID of the process using the port you're interested in, you can just type further on the console:

tasklist|find <PID number>

(without the brackets), where PID number is the PID you retrieved from the previous command.

That should return you the name of the process that's using the port.

Or perhaps... this is harder? :rolleyes:

Share this post


Link to post
Share on other sites

as it happens this is my first time dealing with ports at the cmd so please excuse me for being unsure

all i was trying to do was ask for the meaning of it (cmd's output for the command you guys gave me)

im sorry im not very familiar with the cmd and its commands, i would also like to apologize in case i have not made myself clear enough as english is not my native tongue

greywizard, thank you, i managed to find it the first time

couple of things i need explaining if its not too much of a burden:

1. bitcomet has another tcp listening port (23166) which is not the one specified as my listening port (50039), is this ok?

2. the port chosen as my listening port is shown as "listening" at the cmd, how come bitcomet still shows yellow light?

Share this post


Link to post
Share on other sites

If BitComet's PID really is 5356 then it's listening to two TCP ports (23166 and 50039), this is not normal. Exit BitComet, then restart your NIC, start BitComet again and run that command line again.

LE: The yellow light might be caused by many things, the fact that you ignored the first part of my first post included.

Share this post


Link to post
Share on other sites

sorry was too lazy to go downstairs and check =]

anyways its D-Link DSL-2500U

NIC is what? =x

edit: changed bitcomet's listening port to 50033, restarted my pc/router and it is still listening to 23166 tcp port along with 50033

Edited by MrYumYum (see edit history)

Share this post


Link to post
Share on other sites

cant edit sorry for the double post

as it turns out this is the remote download listening port

disabled it just in case

now it shows only 1 listening port for bitcomet's PID (the one i have chosen)

still getting yellow light though

Share this post


Link to post
Share on other sites

NIC is an acronym for Network Interface Controller

You need to forward your port in the modem too. To do this, open the modem's setup page just like you did for the router, only now the address should be http://192.168.1.1

Then go to the "Advanced" tab, then to "Virtual server" in the left panel. And setup a custom rule, forwarding the port for the router's IP address.

Share this post


Link to post
Share on other sites

Yes, that's the easy way to it. When you're connected to it, go to cmd again and type ipconfig /all and the address you're looking for is the default gateway.

Share this post


Link to post
Share on other sites

hi

sorry for taking so long

as it turns out there are 2 firmware versions for it

first is the one shown here which i am guessing you checked how to forward the ports on: My link

here is the second which is the one i have : My link

guide does show how to forward ports however the strange part is that my modem's front page is missing the "NAT" tab under "Advanced Setup" which i am unable to forward ports without

heres a screeny: aaaaaaaayz.jpg

can you think of anything that would cause this?

Edited by MrYumYum (see edit history)

Share this post


Link to post
Share on other sites

If it were me, I'd be looking at the Port Mapping tab, not the security tab.

Share this post


Link to post
Share on other sites

here's a screen shot for the "Port Mapping" tab:

http://img828.imageshack.us/i/portmapping.jpg/

here's the window the comes up after pressing "Add":

http://img715.imageshack.us/i/portmappingadd.jpg/

(for some reason it wont let me post it as a viewable image, im getting this message saying i am not allowed to use that image extension on this board)

i dont think theres anything related to port forwarding/virtual servers there

Edited by MrYumYum (see edit history)

Share this post


Link to post
Share on other sites

so i talked to my ISP regarding the modem and they said all its ports are open, they also said they do not block ports for excessive use of bandwidth, dont know if i mentioned this earlier but i also tried connecting directly through my modem and i am still getting the "cant listen to port" error every time i switch between my listening ports while bitcomet is open

i hate to keep bugging you but i realy want to solve it. can you think of anything else that would cause this problem?

Edited by MrYumYum (see edit history)

Share this post


Link to post
Share on other sites

"Can't listen to port" does not indicate a blocked port at all. This issue is strictly internal.

If the port is blocked, BitComet will listen to it anyway, but no traffic addressed to that port will ever come through. You will not get an error message as such from BitComet.

"Can't listen to port" means that some other application has already registered with WinSock to take the traffic for that port. Ports can't be shared between applications.

If you get the same error when you change listen ports, then the culprit is almost certainly BitComet itself. We have seen this before. Two instances of BitComet are running, but they're using the same configuration file. When you change the configuration for one, you also change it for the other, which registers the changed port first, so the second always reports that it can't listen.

BitComet can be set to start automatically with Windows. If you have done that but don't realize it, and then you also start BitComet manually (or put a copy of its shortcut into the Startup folder in the menu), then this second instance will encounter this exact issue in this exact way, repeating the error when you try to change ports.

You can use the process list in Task Manager, or download and install the Process Explorer tool (recommended) to see if there's an instance of BitComet already running.

Share this post


Link to post
Share on other sites

This topic has become very convoluted. Your posting only once in a while certainly didn't help very much since before you manage to make another post, certainly everybody has forgotten everything that they knew about it, and have to go all over again through the whole topic.

Besides, it has become very unclear to me WHICH is the actual issue you're complaining about at present time.

At the beginning it was the error you complained about, but later I got the impression that you were having problems with a blocked port (yellow light) then again the first issue was brought into discussion, and so on.

Furthermore, it's becoming increasingly hard for any of us to retrieve your system specs and setup every time we re-read the topic (as we have to parse the whole topic each time and it's become quite long).

So, in order to ease things up a bit and make everything clearer could you do the following:

1. Check the "Read This Before Posting" topic on top of the page, and repost all the info within regarding the configuration of your system (at present time) including model of both your router and modem and all the security software that you have installed.

2. Describe in detail WHAT is the current issue that you're complaining about; if there are several then distinguish between them by numbering them, so that we can address them one at a time.

i also tried connecting directly through my modem and i am still getting the "cant listen to port" error every time i switch between my listening ports while bitcomet is open

This is particularly confusing and I can't make much sense of it. BitComet uses only ONE listening port (as far as BitTorrent transfers are concerned). So, about which "ports" are you talking?

If you're referring somehow to the fact that you're actually changing the port number which BitComet uses, can you explain WHY do you need to do that and WHY do you keep doing it all the time?

Share this post


Link to post
Share on other sites

greywizard-

there, please let me know if you need anything else

about your question, im changing ports for no particular reason, in the past i used to change them to make sure the cause for a slow download speed is because it lacks peers and not because the port was somehow blocked

its a habit, and i wanted verify this error will not make my downloads slower.

both issues that you mentioned are linked, while changing to another listening port i get the "cant listen to port" error, than after a while im getting the yellow light saying the port is blocked

1) What version of BitComet are you using?

--1.26

2) What type of Internet connection do you have (ADSL, etc.)?

--ADSL

3) Do you have a modem? Do you use a router? What make and model are each one of them? Have you forwarded your port?

--router is a d-link DIR-655, firmware ver. 1.34, ports are forwarded

--modem is a d-link dsl-2500u

4) If you have more than one router, be sure to mention the make and model of both devices, how are they connected (i.e. in which connector of both devices is the network cable plugged) and which one of the devices is connected to or is the modem.

Also, if you have more than one computer make sure to mention in this case, to which router is every one of them connected.

--have to pc units, both connected to the router, both have static ip's

5) What version of Windows, Firewall and Antivirus do you use?

--Windows 7 Ultimate 64 bit

--AVG internet security 2011 (bitcomet is set as an exception on its firewall)

6) If you are asking about a specific torrent or file that you have downloaded, make sure that you include the complete torrent name, as well as the complete names of the files and their respective extensions/formats (e.g.: .rar, .wma, .bin, .cue, etc.).

--irrelevant

7) For speed-related issues, please run various speed tests at a site such as speedtest.net (make sure that no other computer is using your Internet connection and that all other programs - including BitComet - are closed, during the tests). Include the results, along with the settings that you are presently using, in your post, so that we may review and offer suggestions to improve its performance.

--there : 1148434616.png

http://img535.imageshack.us/img535/9074/processexplorer.jpg

kluelos-

mm i did check again and the "start with windows" box is not ticked, ive added a screen shot of the process explorer to make sure im reading it right, i can only see 1 instance of bitcomet running there

processexplorer.jpg

Share this post


Link to post
Share on other sites

OK, so from what I gather (out of the entire topic, so far) you were reporting to issues you currently have:

  1. Whenever you change BitComet's listening port you get a "Cannot listen to port" error message;
  2. Despite doing your best to forward the listening port you still get a yellow light.

Let's try to sort out the issue number 1, first.

You need to give a little detail about when the error occurs. Do you just change the port number on the Options page and when you hit OK you get that message? Or do you get it after restarting BitComet? Do you still get it if you restart Windows after changing the port number?

What is the color of the status light after you change the port number (as soon as you receive the error message)?

Now, AFTER you get the error message but as soon as you dismiss it (meaning after the error manifests itself), start a command prompt in administrator mode, run these commands at the command prompt and note down the results for each one of them:

netstat -aon|find /i "oldportnumber"

and

netstat -aon|find /i "newportnumber"

where oldportnumber and newportnumber are the port number before and after changing.

If you get multiple results for any of the commands just replace it with:

netstat -aon|find /i "portnumber"|find /i "listening"

and that should reduce the number of results.

Then retrieve the PID (that's the number in the last column) and use it in the following command (for both old and new port numbers):

tasklist|find /i "PID"

where PID is the number you retrieved from the previous command.

This way you'll be able to tell which process is using the old and the new port number (if any of them is still in use).

And if the results prove there is still a bug in BitComet, we'll be able to forward this report to the dev team.

But in order to do that, you'll need to give an answer to each of the questions or steps I'm asking you to take.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×
×
  • Create New...