Some stupid BitComet problem
Does anyone seen something like this ?
Situation : BitComet 0.80
Router-Modem : Sagem Lifebox F@st
Computer : Pretty good one, no problems at all (I don't think I need to write what it is made of)
I am using internet (1mb/s connection) but 1 minute after I run BitComet, my connections is lost (Windows XP isn't even informing me about it - it seems like it broke down or something). After I disconnect and connect my modem, it works properly again - but it repeats after I use BitComet. I want to download my stuff via torrent, but I unable to. I opened the gates for BitComet in my routers but it still isn't working properly.
I started to use BitComet Tracker 0.4, but I don't thimk that's the case.
If someone knows what should I do, I would be greatful to hear any advice.
Why don't you try a different bittorrent client like bitlord for utorrent and see if you have the same problem.
Maybe your ISP don't allowe use torrent client. But if you use a new client program i think it will solve problem
Ok, I will try and see If I can solve my problem this way - I will give you information if something changed...
Edit : Nothing changed - but I will try some different methods. Thanks anyway...
Last edited by Kolox; 01-01-2007 at 06:06 AM.
change the ports used to 58000 something. That should solve any possible ISP problem. Open/forward the ports you chose in your router to your static IP adress, or use that other method (can't remember it's name right now... I need to bone up on this a bit again) if you use DHCP. After that, check your Firewall and make sure TCP/UDP is open for either that program (allowing internet and server rights) or the ports you specified.
Next thing to do is to start up BT and watch the firewall logs, or use a packet sniffer like ethereal to watch it if you can read that.
Another thing to try is limiting the upload/download and connections per second to low numbers, then increasing them. It could just be that your trying to pump more information through than your connection can handle, thus preventing anything else from getting through.
thanks to Silverwmoon!
It seems I haven't opened the port for my firewall - I will see if anything changes.
Last edited by Kolox; 01-11-2007 at 11:29 AM.