Bearshare 5.25
 

The first LED keeps on blinking from yellow to green, however I can establish connection before, but when I installed Bitcomet P2P program this problem occured. The listening port of this program is 13432. I patched the connect winrar to Bearshare.db. Sometimes the fourth LED is stable to yellow color. It says that TCP is Firewalled. How can I solve this problem. Thanks to coordinators and members of this forum.

Enable the Hosts view and look at what is happening in there.

If you are just getting started: http://www.gnutellaforums.com/host-c...-gnutella.html

Don't forget to [Configure your router for BearShare]

This is the result of the host view: (Ultrapeer Host 217.96.52.70:6328 Horizon In/Out 14058) and (Ultrapeer Host ppp-135-229-33-151.iol.it6348 Horizon In/Out 6866). This time Bearshare is connected but sometimes don't. BTW, the tcpip.sys is renamed by Bitcomet to TCPIP.SYS.ORIGINAL. Now that I opened the Bitcomet program Bearshare is disconnected again. Anything can you give some tips? Thanks!

sounds like you can't use BC and BS at the same time, now doesn't it....

what in god's name BC is doing changing the TCPIP.SYS file is beyond me...why don't you try something like Azureus...

I find that when I'm using the BS beta that it takes up a LOT of resources and I don't use any other p2p program as the same time...the same with a torrent client...just live with the limitations...

Perhaps, you're right. I noticed if BC is not active BS can connect. Thanks anyway.

upon reflection what I'm thinking is that something may not be right with your copy of BC...the changing of TCPIP.SYS sounds fishy to me...unless its some sort of way to try and hide your identity...dunno, I'm not a bitcomet user...

maybe if you try asking here somebody might be able to clue you in:

The BitComet Forum has been moved to BitComet Postbar. Welcome to Bitcomet Postbar! - BitComet Support Team's BLOG

usually I leave such research to the person who wants an answer, but in this case because of a post in another thread my interest was piqued..

it would seem that the file tcpip.sys has to do with the number of simultaneous connections that can be had...in SP2 for xp this was limited to help prevent the spread of worms...I'm guessing BC is using a modified version of this file to allow it to more effectively do its 'business'...the thing is, if it is doing so in a way that prevents other p2p apps from being used at the same type then its bogus...

there is a patch floating around that supposedly deals with this issue, but I've never tried it...I dunno if any tweaks I've done to my system have affected it or not, but I haven't had any issues with p2p since SP2 was released, and I'm currently using SP3...

still, my comments re: use of certain p2p protocols at the same time is valid...when one app uses so many resources then its best to just use that one app alone...