I have BitComet version 1.07, connecting with a DSL modem/router combo. It is an Actiontec Q1000.
Windows Vista OS without the Windows firewall.
Panda Antivirus with firewall, and exception to allow BC.
Previously, with my Cox cable I was set up correctly with a green light, so I am familiar with port forwarding. Now, however, I can’t seem to get a green light no matter what I try.
TCP listen port set to 0 is definitely a problem. I’m not sure how you did that, I didn’t think it was possible to set TCP and UDP to different ports. In your P/O/W for bitComet, what is your listen port set to? I want to find that out before getting into any of the rest of this.
I am unconvinced of any danger at all in listing your iP address, given that it’s just leased and that it will change. But there’s never any danger in exposing a 192.168.xxx.xxx address, since these are all private LAN’s by definition and cannot be accessed from outside. (Most routers will refuse to try because it’s a reserved address.)
In your P/O/W for bitComet, what is your listen port set to? I want to find that out before getting into any of the rest of this.
I’m sorry, I looked everywhere but couldn’t figure out what P/O/W means kluelos. In the options, the listen port is set to 49155, chosen to be in the quick range from the faq’s.
I will try for a fresh install (update to 1.19 perhaps?) in the morning. I’ll do some dl’ing and seeding overnight as the speeds are not that bad. (40-260 kB/s down with 3 files going)
P/O/W is what we call it due to a very ill-advised name-change. They used to be called 'Preferences", then one day we found some coder had renamed them “options”, so all of the answers given before were now confusing. We started calling them Preferences/Options/Whatever-they’re-calling-them-this-week, hence P/O/W. Whatever you understand them as. The program configuration choices.
I’d agree, go with the clean install, this is not supposed to happen that the TCP and UDP ports can be different. That they are suggests something is very messed up in an unusual way.
You should have uninstalled your BitComet version.
You should have manually checked that the BitComet folder in Program Files is gone.
Also, you should have checked that the BitComet folder in Users%userprofile%\AppData\Local\VirtualStore\Program Files is gone, as well.
Only after that you should have reinstalled the last version of BitComet.
Did you go about it like this?
Well I am apparently not getting a clean uninstall. Upon reinstallation, I show files still in the queue, and the port it’s listening to is the old one I had set.
I did all of the above steps, plus checked the registry. I’ll try again. Would you know what file I should be looking for perhaps? I did do a windows search for “Bitcomet” and deleted all of the folders found.
As kluelos said, you should additionally check for the Documents and Settings%userprofile%\Application Data\BitComet folder.
As your previous version was installed in Program Files (I presume) you shouldn’t normally find anything in the AppData folder, but check it nonetheless.
We’re all going here on the assumption that your v.1.07 was installed in the default Program Files folder. If you know it was elsewhere you should check that place.
And you can check the actual path to your BitComet folder, by looking at the shortcut properties page.
