You needn’t be sorry or apologize, I was never offended by anything that you posted. If I were, my post would have been way different. B)
I was just trying to give you another perspective on the matter: OURS. It’s pretty annoying to read a request for help and after going through it to realize that you can’t actually help that person as s/he didn’t give you any valuable info to work with and all that you’ll be able to do, will be to waste your time writing a post where you ask for more info.
We CANNOT trust a user to be a geek who always knows what s/he speaks about, and therefore we always ask for a full description of the setup, in order to draw OUR OWN conclusions, instead of relying on those of the user. After all, if all his/her conclusions were that good s/he wouldn’t be here asking for help, as s/he would have solved his/her issue alone, wouldn’t s/he?
At some point every person who works tech support makes the mistake of taking to his word, a user who seems to “know what he’s talking about” and not double check certain things about the basic info, because the user reported that in that area “everything was in order” or that “he had checked that thing and didn’t find any problem”. Then after lots of back and forth messages, unending questions and tests you’re working together with the user, at a certain point you discover that he unawarely ignored and misreported some very important setup data that would have helped you solve the issue in, probably, a fraction of the time you wasted fruitlessly just because you confided in his technical judgment skills.
This will usually be a bitter reminder for you as tech-support, to NEVER make that mistake again.
This doesn’t mean that all users who ask a question on a forum are newbies or people that aren’t “tech-savvy” (perhaps many of them are way better than us in a lot of areas) but just that, as a golden rule, no moderator on a tech forum will ever trust you to “know better” what info is needed and what isn’t, you’ll have to provide all the boring details, if you **really **want an answer.
And usually, those very tech-savvy almost ALWAYS provide the needed details before being asked, as they can judge for themselves that they’ll be needed.
Now, coming back to your issue, my skepticism, manifested in the previous post, is once again fed and seems to have been well founded.
You say:
as far as i can ell my modem is only a modem
Well, a quick search (it took only 0.24 seconds B) ) on Google proves you wrong and myself, once again right to never trust somebody else’s opinion and draw my own conclusion: http://www.netcomm.com.au/netcomm-products/adsl-broadband/nb7.
You can see for yourself that your “modem” is a combo device which includes a router too. I hope now you begin to see why we can never rely on the user to “interpret” for us the info we need and why we rather need the exact info such as: version, make, model and other details. Ditto for the exact text of the error message and the application is which occurs, rather than what the user “thinks” that it may mean or trigger it.
You can find guides on how to take an upload screenshots of your displayed images in the Guides section of the forum.
Now, this is a good job on describing your problem and that is how you should do it whenever you have a problem (as you did at point 3). I finally understood what you meant.
What I can tell you so far is that the error which you see (as you probably already realized yourself) is reporting a problem with your Internet connection itself not with BitComet. BitTorrent clients place an unusually high stress on certain components of your system and while that isn’t at all bad by itself, it sometimes makes come to surface hidden hardware or software issues lying in the system which weren’t very visible otherwise. That is to say, in this case BitComet is rather the victim than the cause.
BitComet, just as any other BitTorrent client works by opening huge numbers of simultaneous connections to different IPs on the Internet (those of your peers). This usually puts to work and testes to the limit your router (when you’re using one).
My guess (but it’s only a guess so far) is that your router may not be coping with the big number of connections and it crashes or restarts.
Now, we’re going to still need those screenshots, so make sure you post them.
Also we’ll need you to tell us what firewall/security suite/antivirus you use.
In the meantime there are a couple of tests you could make to narrow this down.
-
If you can get your hands on another modem device and replace yours with that one (try borrowing from a friend) just for testing sake, you could diagnose if the problem truly lies with your modem.
-
If you can’t switch modems then try disabling DHT, eMule, LT-Seeding and Torrent Exchange in BitComet. After that, go on the Options–>Advanced page in BitComet and limit the network.max_connections parameter to a low value, such as 200.
If you won’t get anymore network crash issues for a long enough while (a couple of days) you can try increasing the value to 300, 400, and so on, until you find a value that makes your modem crash. Then stay below that value to insure problem-free functioning.
That is, assuming this is the reason of the issue.
*L.E. TUUS, we must have written our replies in the same time, I wasn’t aware of yours when I wrote this above. 
*
