Just a wild thought, maybe try logging into your computer using a different user account & then running WS. Any difference?

Some ISPs provide their own firewall ( & so people can end up inadvertently using 2 firewalls) but if that was the case then I think you'd see issues with uTorrent as well. I can't find any info to suggest that your ISP interferes with P2P traffic.

I'll give that a try, don't have the time right now to set it up though.

Just tried that, unfortunately I have the same issue....basically it's connecting, TurboCharged connection but the downloads are either stalling out right after I start the download or work with an abysmal speed of under 50kb/s.....

Right click on the search tab > find more results.


Change ultrapeers that you're connected to. In WS, go Tools > Advanced Tools. You'll see the list of your ultrapeers - right click on the UP that you've been connected to for the longest time > Remove. Now repeat your search. If no differnce, remove the next UP and so on...

Ultrapeers are unfirewalled users with fast connections who handle lots of search traffic, so changing UPs can change the search results that you see.


Don't forget that the network's dynamic - as users in different time zones log on & off, files being shared (and hosts' bandwidth) will change. So try searching at different times of day.


Try varying your search terms. If you're searching for music, search for artist or album, rather than song title.

Same issue? You were firewalled and unable to connect. Then firewalled but able to connect. You made no mention of download speeds prior to your last post.

Do you share files?

Keep in mind not everybody has a fast internet connection particularly for uploads. Download speeds depends on the upload capacities and upload bandwidth the uploader has remaining.

There's still some people in the world using dial-up connections which means downloading from them at speeds ranging from 0.1 to 5 KB/s. Some satellite and other wireless types of connections whilst offering ok download speeds for the host have abysmal upload capacities not much better than dial-up.

Some hosts might be uploading to anywhere between three to 25+ hosts and their bandwidth divided unequally between them. Their upload speeds will also fluctuate for varying reasons.

If your WireShare is firewalled then it will mean your WireShare will not be receiving UDP messages.

Search and download speeds can be hampered by firewalling. Relying on TCP connections for most communications will mean a lot more overhead as TCP is not the ideal communication protocol.

An example of something different: the speeds between USB-2 which in theory has a speed of 480 mb/s versus the now obsolete FireWire 400. FireWire was actually faster due to USB-2's heavy overhead, in practice somewhere between 15-35+% overhead loss of speed which means it falls lower than FireWire (30-40 MB/s versus about 50.) Sounds like a strange comparison right!? Actually not so strange because TCP also has an overhead and is a notably slower process than UDP. As a general rule, TCP requires a greater amount of communications traffic for the same result as UDP (which has far less overhead and has a faster communication protocol overall.)

I've been using WSHR for some time, thanks for the pointers, I'm aware of how it works :) I'm just puzzled as to why this is happening, it was working fine before I reinstalled my Windows.
The issue I'm having right now is that the search works, SOME downloads work, but most of them just end up stalled, I did a quick test, searched for a song, got like 300 results, I started to download all of them, only 3 downloads actually worked, but the speed was abysmal to say the least.
And yes, I do share files obviously :)

Shared files on the network are cached by ultrapeers. If a host leaves the network or removes some or all of the files they are sharing it can take a notable amount of time before the cached the files are removed by all involved ultrapeers. This can mean one or more hours. That is one downside of DHT for example (though the advantages of DHT outweigh its downside.) So there's a high chance a percentage of all search results are redundant (the host sharing the file is no longer on the network or sharing the file.)

I am aware some people remove their shares mid-way through sessions. They obviously have their program set to automatically share downloaded files (the default of most programs.) I've witnessed this first-hand many times after browsing them. I was able to download one or a few or maybe only a part of a file then it stops. A re-browse of the host shows them no longer sharing the file. This always annoyed the life out of me. :( These are people who probably don't really wish to share files but they are ignorant how to properly configure their program. (I've also witnessed this whilst they were presently downloading from me & has happened many times over the years.)

It appears browse-host can also be affected by DHT as it does not always update the host's shares properly between browses.

Hello,

Some time ago WireShare (version 5.6.6.0) stopped connecting. It was white-listed in the Windows Firewall, anyway I removed it and re-added it again. It did not help. I uninstalled it and re-installed it afresh but to no avail. There is no gnutella.net file in WireShare profile folder:

and I think there has never been such a file. WireShare had been working fine for years but now it simply cannot connect. This happens under Windows 8 x64. Any suggestions how to cure this connectivity problem? If the problem persists I will have to switch to Shareaza.

Download a fresh gnutella.net host file from https://sabercathost.com/folder/117312/gnut_file and copy-paste the file into C:\Users\UserAccountName\AppData\Roaming\WireShare
Keep a copy of the file in case you need it over the next 12 months. After that if needed, download a fresh copy as it should have been updated by then.

Did you not use WireShare for a month or more?
I can't remember which WSHR version but bigjx decided to re-add the code to delete the gnutella.net file if WSHR has not been used for 28 or more days. I don't agree with his approach but that's it. His idea is that WSHR would then download hosts from web cache to create a fresh file but unfortunately the main webcache WSHR uses has been misbehaving over the past year.

Since WSHR last connected for you, have you installed or updated any security softwares? One of them might be blocking the connections.