I have the same problem as many users is haunted by because of BearShare is not connecting to Gnutella network no matter what I do...I know 100% my BearShare is not firewalled, so her I have to think new and figure out a better way then only change the connect.txt file in hope to finally get connected! The BearShare 5.1.0b25 has a forced Ultrapeer function to use which other BearShare versions do not have. I know when BearShare hit Ultrapeer mode it connects to the Gnutella network no matter what, and I started to think is it possible to push other BearShare versions to Ultrapeer mode and get connected to Gnutella network instead of get frustrated by never ever get connected.. I have found a very simple solution to do and kick any BearShare from 4.7.3.2 to 5.2.5.9 into Ultrapeer mode, and here is how!!!

Before you can use the Ultrapeer mode trick below, you must be sure you are not "FIREWALLED" and the "connect.txt" in db folder located by default C:\Program Files\BearShare\db is not to old. Replase it if it is... You will find a new one here if needed: BearShare Connect Fix installer

1.) If BearShare is runnig and trying to get connected and not do so, just exit BearShare so it shuts down completely...

2.) Locate the BearShare installation folder which is by default C:\Program Files\BearShare, and find this file here: FreePeers.ini

3.) Open FreePeers.ini file with any txt editor you like to use like Notepad/Notpad ++.

4.) Find this section [FirewallLogic] in the FreePeers.ini and it should look like the code below:

5.) And change this line from (No): bUdpNFW = No ; yes if Udp non-firewalled.

to (Yes): bUdpNFW = Yes ; yes if Udp non-firewalled.

And copy the Tcpip and add it to Udpip, and the changed code will look like this:

So move on to the next step...

6.) Find this section [HostLogic] in the FreePeers.ini and it should look like the code below:

7.) And change this line from (No): m_bEverUltrapeerCapable = No ; Has client ever been an Ultrapeer

to (Yes): m_bEverUltrapeerCapable = Yes ; Has client ever been an Ultrapeer

And the changed code will look like this:

8.) Save the changes in the FreePeers.ini file, and fire up BearShare and wait a few sec and it will Kick in to Ultrapeer mode and finally get connected...

Edit by LOTR: Also check post #13 about UP expiry date here if BearShare has not been used for a month or longer.

__________________
Just Good enough, smart enough, and no longer Elite...

I was always thinking there would be a way to force ultrapeer but never knew how!
But, I tried your trick, everytime I change "No" to "Yes" and open BearShare it changes automatically to "No" again and it never gets forced to Ultrapeer Mode, any suggestions?

Which version of BearShare are you using may I ask?

Past couple days, I've again tried experimenting with using BS 5.2.6 Pro (k), as usual struggles to make any connections. 15-35 mins may connect to one bs host, at most 2. But we all know those (k) versions of 5.2 do not connect or connect well. At that rate, BS 5.1 beta beats it hands down. I suspect probably the only persons using BS Pro who are regularly using it were original users of the program.

I'm not sure what the improvements of 5.2 were supposed to be, other than UPnP support, I doubt there was any dramatic improvements, also considering the developer was already working on ways to infest the program with external control.
Lovely, they added the (k) version to the BS Block list, AaronWalkhouse was so thoughtful, such a kind person. Especially since he had so much control over the block list.

I use 5.0.2 Pro

There is also the hosts section for forced ultrapeer:
The [Hosts] section is about 10 or more paragraphs before [HostLogic].

Thanks LOTR, please send me the whole section [Hosts], because in my Pro version the "
bForcedUltrapeer = Yes ; Forced Ultrapeer mode" is not included originally in the file.

It Works!

BearShare....can you or LOTR please share the [Hosts] section that has the bForcedUltrapeer within it. I too am running the 5.0.2 Pro version but can't get it to connect.

Thanks

In retrospect, I am not sure the forced ultrapeer option is applicable to the Pro or standard version. I suspect it might only have been intended for testing with the beta. I will send you what i have anyway.

[Hosts]
bUseDefaultServiceProvider = Yes ; always try public.bearshare.net first
bNeverBecomeUltrapeer = No ; never become an ultrapeer
bForwardPublicQueriesToLAN = Yes ; Forward public queries to local LAN via multicast
bNativeCompletionPorts = No ; Use native completion ports for socket I/O
connectTimeout = 10 ; max seconds for connect
handshakeTimeout = 10 ; max seconds for handshake completion
msgTimeout = 10 ; max seconds to receive message
tempTimeout = 5 ; max seconds for temp to send a ping
hostMinorTimeout = 3 ; display time for minor errors
hostMajorTimeout = 10 ; display time for major errors
szAuthUserAgent = "" ; Authorized User Agent
szRejectUserAgent = "" ; Reject User Agent

You have to get an open port on your router to get BS connect.