listen port still blocked- help me out

[nipun1110]

information required as your instruction:

1. I’m using bitcomet 1.21

2. I’m using a 256 kbps wireless broadband connection in Bangladesh.

3. I’m using a modem. no router, but a switch to share connection between two computers by cable. & i didn’t do any forward of my port. my modem is a large size one, supports 4g, made by SIEMENS…

4. I’m using windows 7 & eset nod32 business edition latest version.

5. screen test result is given below ( pic-1)

my problems:

i have tried all the ways to unblock my listen port but wasn’t successful. so i need some help i guess.

• current bitcomet condition is as pic-2 ( which is the best condition ever but the speed fluctuates)

• current bitcomet settings are as from pic-3 to pic-12

• current my firewall settings are as from pic-13 to pic-26

• current antivirus settings are as from pic-28 to pic-46

• current my net connection settings are as from pic-47 to pic-49

now please help me to find out why my listen port is blocked…/monthly_06_2010/post-57709-12769813151249.jpg" rel=“”>

/monthly_06_2010/post-57709-12769810307317.jpg" rel=“”>

/monthly_06_2010/post-57709-1276981168063.jpg" rel=“”>

/monthly_06_2010/post-57709-12769811832841.jpg" rel=“”>

/monthly_06_2010/post-57709-12769812044708.jpg" rel=“”>

/monthly_06_2010/post-57709-12769812205147.jpg" rel=“”>

/monthly_06_2010/post-57709-12769812342357.jpg" rel=“”>

/monthly_06_2010/post-57709-12769812446232.jpg" rel=“”>

/monthly_06_2010/post-57709-12769812615256.jpg" rel=“”>

/monthly_06_2010/post-57709-12769812770701.jpg" rel=“”>

/monthly_06_2010/post-57709-12769812946408.jpg" rel=“”>

/monthly_06_2010/post-57709-12769813821654.jpg" rel=“”>

/monthly_06_2010/post-57709-12769813995222.jpg" rel=“”>

/monthly_06_2010/post-57709-12769814185105.jpg" rel=“”>

/monthly_06_2010/post-57709-12769814355199.jpg" rel=“”>

/monthly_06_2010/post-57709-12769814633208.jpg" rel=“”>

/monthly_06_2010/post-57709-12769815266001.jpg" rel=“”>

/monthly_06_2010/post-57709-12769815603252.jpg" rel=“”>

/monthly_06_2010/post-57709-1276981576296.jpg" rel=“”>

/monthly_06_2010/post-57709-12769815969213.jpg" rel=“”>

/monthly_06_2010/post-57709-12769816223704.jpg" rel=“”>

/monthly_06_2010/post-57709-12769816702054.jpg" rel=“”>

/monthly_06_2010/post-57709-12769817622404.jpg" rel=“”>

/monthly_06_2010/post-57709-12769817841878.jpg" rel=“”>

/monthly_06_2010/post-57709-12769818066906.jpg" rel=“”>

/monthly_06_2010/post-57709-12769818241951.jpg" rel=“”>

/monthly_06_2010/post-57709-12769818330204.jpg" rel=“”>

/monthly_06_2010/post-57709-12769818793605.jpg" rel=“”>

/monthly_06_2010/post-57709-12769819023256.jpg" rel=“”>

/monthly_06_2010/post-57709-12769819145952.jpg" rel=“”>

/monthly_06_2010/post-57709-12769819272746.jpg" rel=“”>

/monthly_06_2010/post-57709-12769820029455.jpg" rel=“”>

/monthly_06_2010/post-57709-12769820155053.jpg" rel=“”>

/monthly_06_2010/post-57709-12769820302947.jpg" rel=“”>

/monthly_06_2010/post-57709-12769820514044.jpg" rel=“”>

/monthly_06_2010/post-57709-12769820690244.jpg" rel=“”>

/monthly_06_2010/post-57709-12769820902045.jpg" rel=“”>

/monthly_06_2010/post-57709-12769821137693.jpg" rel=“”>

/monthly_06_2010/post-57709-12769821316456.jpg" rel=“”>

/monthly_06_2010/post-57709-12769821559589.jpg" rel=“”>

/monthly_06_2010/post-57709-12769821882301.jpg" rel=“”>

/monthly_06_2010/post-57709-12769823606303.jpg" rel=“”>

/monthly_06_2010/post-57709-12769823900306.jpg" rel=“”>

/monthly_06_2010/post-57709-12769824045616.jpg" rel=“”>

/monthly_06_2010/post-57709-12769824264693.jpg" rel=“”>

/monthly_06_2010/post-57709-12769824392693.jpg" rel=“”>

/monthly_06_2010/post-57709-12769824547093.jpg" rel=“”>

/monthly_06_2010/post-57709-127698247078.jpg" rel=“”>

[Vasy]

If I get it right, eset only allows incoming connections from one remote IP address, you should allow everyone to connect to Bitcomet. You’ll know you made the rule right when it will say “Allow” instead of “Specific” next to BitComet in the list of rules.

[greywizard]

information required as your instruction:

…

3. I’m using a modem…my modem is a large size one, supports 4g, made by SIEMENS…

Well, you see, the instructions specifically ask for a make and model for every device you say that you use. The fact that it’s made by Siemens means nothing to us unless you give the specific model for it.

no router, but a switch to share connection between two computers by cable.

The same goes for your switch. You may know what switch you have but we don’t.

Since we have no real info about your equipment we can only take your word for it.

So, I’ll have to guess at best.

If your modem is only a modem and if your switch is only a switch then I can’t see how you would have a wireless connection.

I mean, yes it obviously is “wireless” as in “no-wires” but it can’t be using the WiFi 802.11x standard since in that case you would be connecting through an wireless access point or a wireless router with access point integrated not through a modem.

Therefore, if your modem is really only a modem, then I’d have to guess it’s some sort of UMTS/EDGE/GPRS/HSPDA or whatever other wireless mobile technology your ISP is using.

And if that’s the case, it probably means that you’ll never have an open port on this connection, since most mobile telephony companies are using firewalls on their routers which filter incoming connections before they go wireless.

The other possibility which comes to mind is that you may be using a WiMAX connection and that you have a WiMAX gateway or something (which the 4G might mean), in which case the same reasoning as above may apply.

The thing is, most ISPs providing wireless services don’t offer full Internet connectivity (that is, you won’t be able to run a web server on their connection) and you should ask explicitly about that before you bargain for your contract.

So you see, by providing a simple model number for your modem and switch you would have saved me from guessing a lot and yourself from posting **49 **screenshots which may prove ultimately useless.

[The_UnUsual_Suspect]

If (and I do stress “if”) your using a cellular broadband connection and are behind a router under control of your ISP, AND they offer no designated port for you to use, then your choices are very limited.

1. You can use bitcomet without a listening port. This is very inefficient, as no peers can connect to you when “they” need connections, only you can initiate a connection to them, and it’s a matter of luck if you reach a good peer when they are looking for trade (unchoked).

2. You can install a version of BitComet that supports NAT-Traversal. This is a technology that was discontinued to improve tcp connection efficiency, but it’s sole purpose was to bypass the problem of not having an open listening port. Version 1.02 was the most recent to have NAT-Traversal. You can get it, and all previous versions from our archives at BitComet.com

Additionally, users with very limited bandwidth can reduce some of the overhead by disabling some or all of the bitcomet services. Some of these services can help speed up your downloads, but only if you have available bandwidth to make use of the resources they discover. In your case they are probably just slowing you down.

I hope this helps

[nipun1110]

well ya i am sorry that my information wasn’t complete enough to help u to help me out…actually i do not understand all these things too much as i am a doctor… well i can clarify that i am using a WiMax connection n a TP-LINK(TL-SF10005D) 5 port switch. Is this enough to clarify u? N i am getting the net connection wirelessly whereas my other partner getting it from my pc through cable through switch… I really wish u will be able to help me, if any other informations needed, just ask that…

[kluelos]

Unfortunately for you, WiMax is all we needed to know.

Wireless connections like WiMax are distributed as a subnet off of the internet proper, which means that they pass through a private wireless router owned by the WiMax operator, your ISP - Clear or whoever. Such routers are, almost always, firewalled to block unsolicited incoming connections.

The WiMax connection is sold to people who generally do not need any incoming traffic. That is, they don’t run web servers or email hubs or the like. If you need to do that, you need some other sort of connection. Unsolicited incoming traffic is blocked, and that will include P2P connections. You can still make outbound connections, but the net result will be very slow transfers most of the time.

I’m afraid there’s nothing you can do about that as long as you’re using the WiMax connection. You’ll just have to operate in “No Listen Port” mode and live with the resulting speed.

[greywizard]

The best you could do is try to talk to your ISP about it and see if they can be convinced in any way to sell/give you a full Internet connection.

In the unlikely (and happy) event they say they don’t block your ports, then and only then you should start troubleshooting your local network.

[The_UnUsual_Suspect]

I will repeat that you still have the “less then perfect” option of using a version that supports NAT-Traversal. If you want to try one, you can get version 1.02 (most recent version supporting NT) from our archives at bitcomet.com.

Don’t expect it to magically fix your problem, but peers using a client that supports it can ultimately connect to you.

[nipun1110]

thanks a lot for helping me… one last question- why u referring me to use 1.02 version where i am using 1.21

[greywizard]

2. You can install a version of BitComet that supports NAT-Traversal. This is a technology that was discontinued to improve tcp connection efficiency, but it’s sole purpose was to bypass the problem of not having an open listening port. Version 1.02 was the most recent to have NAT-Traversal. You can get it, and all previous versions from our archives at BitComet.com