@runt66

It seems that you are right- I installed version 5.6.6.0 over version 5.6.5.0 again and the latest version failed to connect again. I downgraded to version 5.6.5.0 and it connected immediately. The only nuisance is that I don't find a way to disable update check on program start- I browsed through options but I could not find such an option. Is there a way to disable update check?

@Lord of the Rings
For me the penultimate version (5.6.5.0) is better than the latest version (5.6.6.0) since it does not have problems connecting. If it is possible please notify the WireShare developer about these connection problems in version 5.6.6.0. I would appreciate a new version which would resolve these connectivity problems introduced in the latest version.

Can be random. I've always had port forwarding set for 5.6.6 - no connection issues & never showing as being behind a firewall.

Two days ago very slow to connect & showing as being behind a firewall once connected. Instead of resetting the router config I simply changed to UPnP within Options... instant turbo & not behind a firewall. Uploading fine.


Maybe UPnP success is a bit dependent on the router used? Who knows.

I've likewise had no issues connecting with 5.6.6 which runs long sessions. Whilst I have a suspicion what might cause some 5.6.6 connecting issues for some people I'm not definite.

(original image showed all songs by same artist)
As a moderator I was able to see your deleted post and took a snapshot excluding the file-names. Yes it was off-topic. Unfortunately, WireShare has built-in presets for uploads including queueing. I increased this 5 years ago to overcome some extreme buggy behavour (such as occasionally auto-banning hosts trying for their first file to download.) This is unlike LimeWire v.4 where you could change the upload slots per host and overall and unless I'm mistaken also change the queue size. To my understanding very long queues are not good for the ultrapeers which help manage a host's uploads to some degree (at least that's what a lime dev hinted to me last decade.)

There's not a lot you can do to fix the problem. Perhaps increase the overall upload slots but that's about it. There's still a built-in limit of slots per host that cannot be overcome in settings. I know, it's sad. LimeWire v.5 was obviously not designed with big file-sharers in mind. That was obvious from day one of the LW 5.0 alpha-beta release. That's one reason why I was never over keen about LW 5.

Edit: For a group of related files such album downloads, some exception should be made. A few years back I pencilled in techniques how this could be achieved as exceptions to standard slots per host.

Hi guys, I’m sorry I’ve not been available to help with this issue before now but let’s see if we can get a fix to this issue.

First, I don’t believe there were any changes to the connection code in v5.6.6 (a browse of the commits should confirm this) and the only change was the integration of the Security Level selection and the ability to auto-update the hostile hosts file (Thanks to LOTR for maintaining that feature and doing an outstanding job!).

Next, since v5.6.5 does not have the security auto-update feature and the hostile hosts file is installed from static files within the installer at install time. The issue may be with one of the updated hostile host files. I have seen connection issues happen if the hostiles file had a typo in it or corrupted data. This would also explain why some have the issue and some don’t. To test this, with v5.6.6 installed, try selecting “None” in the Security Level selection and restart WireShare and see if it will connect. If it does connect then try each Security Level to see which one has the issue and post the results here so we can investigate it.

Other than that, I have no clue what could be the issue.

BigJx

Agreed. There might be a hostiles file problem (I recall one time the issue was a blank line.) It might also be a question of which hostiles you chose. I use Hostiles Light NJ without any connection issues.

Problem found. Hostiles NJ had a listing drop back onto the previous line and leaving a blank line. One or the other caused the problem where all connection attempts were failing. File fixed and uploaded ready for updating.

WireShare 5.6.6 will be updated with the fixed version including updates for all hostiles variations of files when you next start this program version.

Why the hostiles updates? Better protection yet more hosts to connect to! Removed many redundant listings where the original listings addresses have since changed purpose, whilst adding fresh hostiles. A list of reasons is provided here http://www.gnutellaforums.com/open-d...tml#post378098 even though it is the BearShare section, same principles apply.

Thanks LOTR for finding and fixing the error so quickly. I can’t say enough about how much I appreciate all that you do for WireShare and the Gnutella Forums community.

Again, good job!!

BigJx

Thanks for all the work on this!

Now, Has the file been re-named? How can we tell/check what we have running?

The security files are maintained online and once WireShare 5.6.6 is restarted it will automatically update the file to the newest version based on your selected Security Level. The file that was causing the connection issue was associated with the "Strong Security." Security Level setting. That file has now been fixed as LOTR said and will be automatically updated once WireShare is restarted if you use that Security Level setting.

BigJx