an update for my post …use utorrent /nothing wrong with port /nothing wrong with any of my sytem settings /.
conclusion …there is most definatetly …something that bitcom isnt telling .
adeos amigos ,you won’t find me here again .
@Zelat0r: It’s virtually impossible to give you an straight answer based on the nearly inexistent information you gave about your setup and the steps you followed so far in order to fix that.
A few posts above I’ve indicated the minimum necessary info from which one may start to draw a conclusion.
A few pointers though, are these:
you need a unique port number for every machine running a BitTorrent client on your LAN. And that port number must be forwarded towards that machine on the router;
You also need a static IP set up for that machine; that IP you will use on the forwarding page of the router.
But if you really can’t solve it you need to start providing all the info required.
@docdoob: Actually, most routers I’ve seen don’t have a SPI (Stateful Packet Inspection) option, separated of the firewall. But it’s good to know, anyway, for those using the same model as you.
docdoob, that’s a pretty strange configuration, but whatever.
“My firewall is turned off. So I’m going to, what, just look these packets over but not do anything with them…” the purpose of this eludes me.
Sounds like it didn’t work for them either, so Huwaei didn’t implement it that way. They just left everyone confused about it.
I really dislike using UPnP for router configuration. It seems to have surprises like this in store when it does actually work.
can anyone help me out ^.^ ; ;
Your message makes my head hurt. I started picking it apart, beginning with “What’s XP Black?”, and going on to tell you about the invention of punctuation and the paragraph, when my system crashed. Probably just as well.
Why not ask your question again, making liberal use of those two innovations and providing lots and lots of information, like whether you have a router of some sort, and what sort that might be? Things like that, you know?
never mind i have given up on Bitcomet lol
never mind i have given up on Bitcomet lol
It doesn’t matter you give up BitComet. BitComet is a free software. But I think you will give up next according to your attitude towards problems.
All BT clients act the same, if you do not setup properly, it can not get the optimal performance. If you just want to igonore the problem and switch to another whenever you have any questions, you will never be able to get best download speed with any BT client.
Sophia, as a Spanish proverb says (even if kluelos, thinks that they’re all very weird :lol:)…
“You could have said it louder, but not any clearer.”
Since the past five six months; I’m struggling to get the green light. Sometimes it gets green; mostly it shows orange; with serious lowering in the download rate.
The thing I want to know is, if this is triggered by the ISP, will forwarding the port do any good. The thing is my ISP sucks in the tech division; I’ve asked for my DNS address several times; but they are not providing it (God knows the reason). So if port forwarding is useful even if the ISP has blocked bit comet’s IP ranges; I’m planning to go to the higher authority to get the DNS (I didn’t find that in my MODEM’s status section; so ISP is my hope now.
**How I was happy with the performance of BitComet till all this mess came along ! **
**Still the same issue; logged into the comet passport in 1 second; but status shows ‘Detect failed’ and is gray. **
Checked again, to get ‘IP BLOCKED’
**Tested the same with U & Bit torrents; which went to green in under 3 seconds. I guess my ISP is responsible; is there any hope for me via port forwarding ? **
Configuration:
CPUs : Intel P 4 HT 3 & AMD Athelon 2.4
OSs : XP SP3 & XP SP2; both 32 bit
Connection : 2Mbps broadband
Modem : Nokia Siemens C2110
**Bit Comet Versions checked : 1.15 - 20100111 (beta); same issue in all versions. **
You do seem to want to blame your ISP. They’re probably not an issue. It’s more likely to be your understanding.
For example, you say, “I’ve asked for my DNS address several times”. At once the question indicates that you aren’t clear on what you’re asking about. I have to guess at what you mean.
Do you seek the IP address of the DNS server? Or do you seek your own IP address?
The former isn’t going to be any kind of secret, and they will answer immediately, but you do need to ask the question properly so that they understand what you want, viz, “what are the IP addresses of your DNS servers, please?” Or you can simply plug in the addresses of the free servers from OpenDNS (google em), or the free DNS servers from Google at 8.8.8.8 and 8.8.4.4
If it’s your own IP address you want, then you do not need the ISP’s help and you don’t need to take up their support time, to find this out. Just browse to whatsmyip.com to find your own IP address. If you are connecting via a router (this is critically important information), this will basically be the router’s IP address. Your computer will have a different one which the IPCONFIG utility will tell you. Your ISP can’t help you with that, it’s your subnet and not theirs.
The most common case, and yours appears to be one such, is that you have one or more firewalls blocking your listen port. Commonly this is not because of your provider, it’s because of your own system settings.
Your best bet there is to start reading this thread over from the beginning. You will find all of the information you need here, and several examples. You’ll need to work through this to the point where you understand exactly what it is you’re trying to do.
**I don’t want to sound rude; but have you ever heard of dynamic IP ? (192.168.1.2/255.255.255.0/192.168.1.1 - for about a billion users)Mine is such a connection; where both IP & DNS are assigned automatically by ISP server. **
**I didn’t know IPCONFIG will provide IP & DNS in a dynamic connection :lol: . Also, most of the public DNS from OpenDNS failed to have a fix on the link (mine is an ‘always connected’ connection), so I relied on ISP, once again. And on the tech issue; where I’m from; the techs do not know how to differentiate a pink elephant from a router. I’m having a faulty line since a week; with about 2-3 written complaints to the L-1 tech; I’m still waiting for something to happen. On asking about DNS; they simply are saying they do not know much about that; contact the higher authority ! World is a funny place sir, if you think everywhere you have the same standard; I’m sorry to say you are terribly WRONG. (P.S. I’m from India; that kind of gives you the picture of the ‘techs’ who are employed in public firms) **
I hope this helps..
http://i228.photobucket.com/albums/ee148/red_ninja_blaze/JUNK/2.jpg
I’m sorry to break it to you but you are in error and you don’t even know it.
You seem to be at that particular point where you got some networking notions but not all the notions which allow you to get a complete and correct perspective of a network setup.
Let’s take it, one step at a time.
First of all you fail to read and understand well, even the posts made in reply to your questions. I say that because kluelos has specifically told you in his previous post that you must first take into account if you use a router or not. As you mentioned in your other topic you have a modem/router device Nokia Siemens C2110.
We can’t guess if it’s working in bridge mode (thus giving your PC a public IP) or in NAT router mode (thus assigning a private IP to your PC).
But since you mention the 192.168.1.x IP range I have to assume that your PC has a private IP assigned to it, by your router.
For your information, the ipconfig command always provides you with the IP assigned to your computer. And with a DNS address. It just so happens that if you use a NAT router these will be local private IPs, not your public IP.
The public IP (which can also be dynamically or statically assigned by your ISP) will be held by the WAN interface of your router in that case. Many times that can be found on the Web interface of your router.
As kluelos also told you (but you failed to understand), in that case your public IP address can be easily found by navigating to a site such as whatismyip.com which will always tell you your public IP, no matter how many NAT routers sit between you and the Internet.
OTOH if you only have a simple modem or your modem/router is in bridge mode then an ipconfig command will show you your public IP and DNS, irrespective if they are dynamically assigned by your ISP or not.
I hope that by now you managed to understand that whether your IP is dynamically assigned to your PC or not has no bearing whatsoever on the results of this command. If you get returned by it either your public or some private addresses, it depends only on your local network setup (using a router or not).
Furthermore, the screenshot you provided is related to Reverse-DNS which is an entirely different thing than DNS. You really need to make an effort to read, inform yourself and understand a notion before using it as an argument in a debate.
Last but not least, I’ve already answered you in your other topic, that the behavior of your BC client seems particular to a UPnP mapping which doesn’t succeed all the times. And I recommended you to disable UPnP and perform a manual port forwarding as a means to get a constant green light.
Your reply was and I quote “I tried the port forwarding; but it secures the same traffic rates; so I switched back to UPnP & dynamic/random port scheme”. So you dismissed my advice and returned to your previous setup.
But the real question was: Did that fix your yellow light for you or not? And why did you return to your previous setup if it didn’t show better rates?
Besides in this very topic you seem to contradict your previous statement and say: “*Sometimes it gets green; mostly it shows orange; *with serious lowering in the download rate”.
So which is what?
And if you dismiss our advice and have it your own way, what exactly is it you would want us to do?
You need to either acknowledge that your networking knowledge is not sufficiently advanced and take to heart and learn what others tell you on that matter or if you believe you know enough, try to solve your problem on your own.
Because if one moment you ask questions and the next moment you think you know better, then you’re only waisting our time. And yours.
You do appear to have some holes in your understanding. Reading this thread, from the beginning, will correct most of those. It was written exactly for people whose understanding of networking is insufficient, and especially for those who’ve learned just enough to confuse themselves.
All of your questions are answered, but you do have to read it for yourself.
I’m surely no network admin; but I guess I did every possible thing to make BC work, and it didn’t.
-
IPCONFIG; got my Default Gateway from there.
-
My IP & DNS (default) are not the same; hence going for port forwarding.
-
Chose a similar ID to my router’s IP.
-
Got DNS from ISP.
-
Entered manual IP, subnet mask, & gateway. Entered DNS server addresses.
-
Chose port address between 49152 & 65534 in BitComet options.
-
Unchecked ‘UPnP Port Mapping’
-
Disabled every restriction & filtering in Router.
-
Restarted both Router & PC.
-
Disabled firewalls & AV tools.
Still, the status is ‘blocked’; in BitComet.
With every other torrent clients working perfectly without any port forwarding; I wonder whats happening here. My humble conclusion still points either to my ISP or to a possible bug.
- My IP & DNS (default) are not the same; hence going for port forwarding.
The thumb rule here is to compare your IP and the Default Gateway IP not the DNS IP. Of course, when you use a NAT router the Gateway and DNS IP will usually be the same as the router’s IP (the LAN bridge interface) so that still works.
- Chose a similar ID to my router’s IP.
I assume that by this you mean you chose an IP using the same base network address and netmask (i.e. if your router/gateway has 192.168.1.1 you should choose something in the 192.168.1.2-192.168.1.254 range).
- Got DNS from ISP.
Most ISPs which assign dynamically IPs to their users, also communicate automatically the DNS servers to the connecting client, so unless specified to do so by your ISP you shouldn’t need to bother to assign DNS servers to your WAN interface (unless you want to assign other DNS servers than your ISP’s). As for your LAN bridge it will use the same IP for DNS like the one for the Gateway (a private IP).
- Entered manual IP, subnet mask, & gateway. Entered DNS server addresses.
Entered where? You need to set a static IP for your PC but for some routers you might want to even removed the address you assigned to your PC from the DHCP pool so that it wont be assigned to another computer if it boots into the network before you do. The method to do that depends entirely on your router type.
With every other torrent clients working perfectly without any port forwarding… My humble conclusion still points either to my ISP or to a possible bug.
If your ISP would be throttling BitTorrent traffic, it didn’t care what client you use. They just analyze and cap a certain traffic type, that’s all.
As for the other clients, it only means that they succeed to map your port through UPnP as you reported BitComet to do on occasions. You can’t tell if they would fail sometimes as well, or not, since you haven’t used them for a long enough period. If they would all the time succeed to map the port through UPnP then it meant that somehow they made better use of the UPnP implementation present in your Windows version.
Or maybe they bypass it and replace it with their own (I really don’t know enough about the inner works of UPnP to give you an informed opinion on this particular detail).
What I didn’t really see in your list above is the part where you actually performed port forwarding.
Did you forget to mention it or you forgot to do that?
Check this Wiki FAQ topic for more details (when you get to the port forwarding part, head directly for the Manual forwarding section).
**“Did you forget to mention it or you forgot to do that?”- - :lol: **my bad; in all that listing; i 4got to mention that..
I logged on to my router’s IP, entered the static IP that I chose ( in the port 4warding section), listed ‘application’ as BitComet; then entered the port number I chose in the place of:
*** ALL TYPE**
*TCP
*UDP
and applied.
In router status menu; (after refreshin the router), the port was successfully entered & was OPEN. Tried changing the IP, and the port number; but no use.
In the past 3 years; I started with Bit Torrent (no issue ever regarding this; even if somthing came up; was resolved by “check again”), U-torrent (never, but was slow) and Vuze (occassionally; but replaced it due to it’s resource consumption).
I had no issue regarding this ‘status’ till 2-3 months (or sooner) since 2008; when I started using BitComet & stuck with it because of it’s performance.
Post some screenshots of your router port-forwarding web page and of a command prompt window with the results of a *ipconfig *command.
Something is obviously wrong, so we need to double-check all the steps you took.
If you need guides for posting images you can find in the Guides section of the forum.
What you basically have, it appears, is a firewall blocking your listen port. A new firewall? It’s quite possible, one you didn’t realize you were installing. A change to an existing firewall that you didn’t realize occurred? That happens too. Something in this situation clearly changed two months ago. You will need to find out what it was.