Initiation = Local

[curlerv]

Hello and HELP!!

I have read posts, change listen setting and well have tried everything and still I have Initiation all showing Local. I am running WinXP home edition, with SP 2. I have a Microsoft router mn-500. I have enter listening port 58xxx in bitcomet, in my router setup - in both the Application-Triggered Port Forwarding (this one is just the program name and port number) and Persistent Port Forwarding (this one requires the ip address) and finally in my windows firewall. Trying to do some narrowing of the possible problems - I completely disabled the router firewall - no results, and then windows firewall - no results, and then I diabled both - no results. I have tried numberous number between the 50000-60000.

On one of the post I read, there was something about your IP blocking incoming request? On that I have no clues. Can someone elaborate on that subject - how to "open" the port.

Any help would be greatly appreciated - I have been reading posts, FAQ, help and trying all the links to see if anything works, but.... no luck. I am showing numbers in the download and upload areas.

Thanks ahead

[petch01]

Try to use ONLY single-port forwarding (don't know if that's the name in your modem/router), not port-triggering. Check with http://www.canyouseeme.org/ whether the port is indeed open.

Good luck.

Petch01

[kluelos]

You left out anything in your description about setting a static IP to forward the port to. For some reason, a lot of people think they can skip this step or that it doesn't matter. It does. A lot.

If you haven't done that, it doesn't matter what else you did, it's going to work only temporarily or not at all.

It is, btw, an extremely bad and dangerous idea to disable all of your firewalls, and you will need to reconnect at least one, then thoroughly disinfect your system with antivirus, AdAware, and Spybot S&D.

[curlerv]

Well.... I think I did the static IP forward part also... Just checked I did the ipconfig and set the ip forwarding to my static ip so yep did that to... anyother suggestions?? I checked the canyouseeme.org and my port is still not recieving... HELP!!

[The UnUsual Suspect]

If you have any other software firewall and/or security software installed, make sure your bitcomet has full access, inbound and outbound.

In most cases this problem is in your router, if possible, connect your computer direct to your modem, see if this makes your port open at canyouseeme.org. If not, then you have a problem in your computer. If it can see the port, then the problem is in your router.

I suggest you review the setup guides at portforward.com.

If I understand your port correctly, you have installed a program to open your port. I recommend you do the setup manually, as it is not that hard to do. You could even call your routers tech support line to request their assistance if necessary.

Suspect

[curlerv]

Ok well after hours and hours of reread and resetting here is what my log says:

Default tracker optimization rules file loaded.

IP rules file: ipfilter.dat loaded, 0 entries.

Start Listening at TCP Port:9093

Start Listening at UDP Port:9093

BitComet 0.70 is running on:

CPU : AMD Sempron 1202 MHz

RAM size : 991.48 MB

OS Version: Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)

Windows XP ICF Status: Firewall TCP port is opened.[Local Area Connection]

Windows XP ICF Status: Firewall UDP port is opened.[Local Area Connection]

Update Local IP: 192.168.2.12

Windows XP ICF Status: Firewall TCP port is opened.[Wireless Network Connection]

Windows XP ICF Status: Firewall UDP port is opened.[Wireless Network Connection]

***Windows XP WF Status: TCP Port is not opened in Windows Firewall.

Windows XP WF Status: add TCP port in Windows Firewall Succeed.

***Windows XP WF Status: UDP Port is not opened in Windows Firewall.

Windows XP WF Status: add UDP port in Windows Firewall Succeed.

I have starred my concerns - is it open or not?? what is ICF and WF ??

Maybe everything is fine I just don't know.

Thanks again

Googled and found ICF=internet connection firewall WF=windows firewall - didn't help but atleast I learned something new today ;)

Edited December 4, 2006 by curlerv (see edit history)