port toggling & bc dc

[MrYumYum]

hi, i want to ask whether it is possible to toggle between knows ports every once in a while, ive noticed my ports beeing blocked about every 20 minutes or so (im suspecting its my isp since it only happens during mid-day times ard 10 AM-8 PM), after switching to another forwarded port it seems i get the green light for another 20-30 minutes...

another thing ive noticed is my bitcomet suddenly crashes/restarts after downloading to the full extent of my bandwidth for couple of hours, which is realy unfortunate especially at nights, is this a known bug or something?

thanks in advance =]

edit: heres the info:

1) What version of BitComet are you using? 1.18

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

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? modem: motorola sb5100, router: tp-link wr541g, ports are forwarded

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. irrelevant

5) What version of Windows, Firewall and Antivirus do you use? windows 7 ultimate, avg9 antivirus, am using windows 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

Edited February 6, 2010 by MrYumYum (see edit history)

[kluelos]

That is almost certainly not happening. I could make a much better estimation of what is happening, if you had provided the basic information that we ask you to provide before asking for help.

[MrYumYum]

sorry about that,

1) What version of BitComet are you using? 1.18

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

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? modem: motorola sb5100, router: tp-link wr541g, ports are forwarded

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.irrelevant

5) What version of Windows, Firewall and Antivirus do you use? windows 7 ultimate, avg9 antivirus, am using windows 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

[greywizard]

Here's an idea. Try connecting your PC directly to the modem. Run it that way for some time.

This way you'll make sure that the problem it's not related to your router.

[MrYumYum]

hmm.. imma try that tonight it might solve the ports beeing blocked, and if it works i cant count on that since im not the only one using the internet here.. but i dont see how the router can cause my bitcomet to crash in the middle of downloading?

Edited February 6, 2010 by MrYumYum (see edit history)

[greywizard]

Who said that I was trying to give you a reply to both your problems in one answer?

Have you encountered so far, a magical solution which solves all your problems in one shot?

I sure haven't.

And no, there is not a known bug regarding BitComet running for long periods of time at full bandwidth speed.

I've run the current version of BitComet for long intervals of time at my line's full speed, both on XP and Windows 7 with no problems of this kind. So, you'll have to dig a lot deeper than that if you want to find the roots of this.

[MrYumYum]

ic.. no need to be so harsh dude i just thought you guys might have ran into this kind of thing before thats all..

[greywizard]

I'm not being harsh. Just pointing out that my reply was referring to your first question.

As for your second one... you'll have to do more deep searching. Such as: looking into your system error logs, trying to set your max download speed to something lower than your max, limiting the number of total connections for BitComet, keeping your Win 7 up to date (some of the updates actually may update the TCP/IP stack too), etc.

(I'm assuming that you have capped your max upload rate in BitComet to 80% of your tested upload speed, as you should, haven't you?)

You could also try and disable your firewall (only if you have the hardware firewall of your router enabled) and disable UPnP (both in BitComet and Windows). Do all this stuff one at a time, then leave the system running for a while. If it doesn't crash anymore, then you might have been lucky and found the problem.

You might also want to use some CPU, memory and system testing tools and benchmarks, in order to test/stress the system, to see if there is any hardware fault hiding somewhere. BitTorrent clients put more stress on a system than a whole lot of other applications, so, sometimes, they simply bring out to light underlying hardware problems.

CPU and memory (use a tool like memtest86+) should be the first to undergo testing.

There is no easy guessing in this cases (crash).

The development team tests the client on several different systems and operating systems, and pinpoints most of the bugs before releasing a new stable version.

However, nobody can reproduce all the possible combinations of the hardware/software environments every user has.

But in order to determine if there is really a bug or just a hardware fault/software conflict on your machine, you'll have to perform some more extensive testing, as said above.

[kluelos]

Regarding the port closing, and now that we know you have a router, the symptoms you describe are typical of failing to set a static IP between the computer and the router. If you don't do that, your computer's IP address remains dynamic, which means it can be and often is reassigned by the router from time to time.

When that happens, it's not that your port was closed, it's that your computer moved out from under the open port which was at that particular address only. A dynamic IP is leased by the DHCP protocol, whether from your IPS, or from your router. That lease can and does expire, and of course is lost when you disconnect from the router for whatever reason. This is commonplace. Your computer simply applies for and obtains another lease, maybe or maybe not at the same address. You're usually unaware that this even happened.

People are warned, in bold print at portfoward.com, that they must not skip the step of assigning a static IP to the computer so it doesn't move out from under the open port, but it's very frequently overlooked, with results as you describe.

[MrYumYum]

Regarding the port closing...

i see.. thanks for teaching me something new =] i thought binding an ip address to my mac address (from my router) was enough?

anyways i set up the static ip, hope that fixed it

Edited February 6, 2010 by greywizard
Removed full qutation (see edit history)

[MrYumYum]

well it doesnt solve the ports beeing blocked, i still have to switch ports manually every once in a while, maybe it is my ISP after all.. is there a software that can switch between several default ports after some time? hope it wont restart anymore though..

[greywizard]

Is UPnP enabled in BitComet? (If yes, disable it.)

[MrYumYum]

Is UPnP enabled in BitComet? (If yes, disable it.)

it is disabled both in my router and bitcomet, anyways it keeps restarting as well (all downloads/uploads seem to stop after a period of time) =[

Edited February 7, 2010 by MrYumYum (see edit history)

[kluelos]

It's good to check whether things have changed on you. When you get a closed port again, check your computer's IP address to assure that it's still where you set it. Check the router to assure that the listen port is still forwarded to the right address.

They probably are, but it's a good idea to eliminate this as a factor.