There is an off-chance that 5.6.6 does not work due to the same firewall problem which 5.6.5 has but not "fully" if that makes sense.
I don't know what else I can do...honestly.

There is one last thing you could try ; if possible ,please go to update and security in your windows 10 settings , click on troubleshoot ,click on incoming connections ,select the last option which is something else ; this is where i am stuck and going batty ; they want wireshare in some exe form or format ; good luck

All you have to do is point it to the wireshare exe file which by default is located in Program Files (x86) -> WireShare.
Good idea, sadly it didn't solve anything...
I think the problem is between Windows 10 and WSHR...for sure.

I received a message about someone's experience with Win 10.

She reinstalled Win 10 a few months ago. Two out of three apps connected beautifully straight away after setting the forwarded port within these program's options. But one was problematic with firewalling.

In the end, to fix the program with firewall issues she removed that program's rules within the router firewall settings & within port forward settings, apply the changes, re-do the Windows firewall & Port Forward settings (using the same port number used previously), apply the changes, restart the program & it worked happily.

She installed WSHR 5.6.6 & set to UPnP and had a turbo connection within about 2 mins. Switched to manual PF using a port already forwarded within the router... turbo again. Removed the small gnutella.net & replaced it with the larger MediaFire download... turbo again.

Note: When you install WSHR it will most likely ask whether you want to allow WSHR to make changes to your computer. Clicking 'Yes' will make an exception in the Windows Firewall for WSHR.

So removing both Windows firewall and port forward rule(s) for WSHR and re-adding them might fix the issue.

Yes, that was me lurking in the background


evil4ever - slight differnces here: I didn't have WS running successfully before reinstalling Win 10 (use other Gnutella clients mostly).


When I did download WS yesterday as a test, it had a gnutella.net file. Almost half the size of the gnutella.net file hosted on MediaFire but nonetheless something there. I wondered whether maybe the WS that you originally downloaded was a bit corrupted (hence you had no gnutella.net file to begin with)? Did you download your version of WS after reinstalling Windows or did you have the installer saved?



And my problematic app was uTorrent. Phex & GTK-Gnutella connected without a problem but for some reason uTorrent was stuck despite going through all options several times. Even though it's not WS, still a p2p app with stubborn connection failure!



And as LOTR said, my fix was completely removing all rules within router config (didn't tuch Win firewall at all), rebooting the router & starting from scratch.

I already tried all of that :/
My router's firewall doesn't have any settings, just an Enable/Disable function.
I recreated WSHR's firewall (windows) exceptions a few times....
uTorrent works out of the box with UPnP...

How about the virtual server section? https://portforward.com/tp-link/tl-wr940n/

(portforward.com did not have this specific model on the TP-Link list but I found it via google. Not the first time this has happened, it's happened a few times. I presume they sometimes forget to add new models to the main list.)

This is the actual port forwarding method. Don't use the xbox port mentioned, select a port of your own choosing and ensure both TCP and UDP are enabled for the process.
If ... ... then it might be worth re-trying.

Also ensure you have a static internal ip address as noted in post #8. Otherwise the next time you start your computer the computer might have a different internal address and the port forward rule no longer works. Port forward rules are set to specific LAN addresses.

Sorry for the lack of a reply, I got sidetracked by more important stuff.
I re-did the settings, the port forwarding, everything, I'm still showing behind a firewall but the dropped messages % dropped close to 0%...
I don't know if there is a fix for this...
Initially I removed everything, the port forwarding, the firewall exception.
Started up WSHR and after a while of trying to connect it prompted me for the firewall exception so I clicked allow, after that it managed to connect - a note here, the port forwarding was not set to UPnP, it was set to manual but the actual rule in the router's settings was not set either....I went ahead and set that up as well.
Here is how the connections look like:

Thanks for going to the effort of the snapshot hosting. I apologise and hope you don't mind but decided to edit the image so that it does not list the entire address of the hosts for their privacy. I also shrunk the image slightly.

Glad to see you are able to connect. However it would be preferable if you were able to fix the firewalling issue. Something is amiss. Either the UPnP is not working as it should or the port forwarding process is not properly set-up or something else on the computer's set-up is causing the firewalling. The question is to figure out what is causing the firewalling. It's my guess it is purely UDP firewalling and TCP is ok.

Keeping in mind UPnP and port forwarding are two different independent approaches to battling the NAT issue with routers. Only one can be used at a time.

If UPnP is used then it needs to be enabled within WireShare and if the router has a UPnP on or off option then it needs to be enabled.

Portforwarding requires the manual port setting within WireShare, and a TCP and UDP port forward rule set within the router. With your router I believe the port forwarding rule is referred to as a 'virtual server' rule. Some routers you can set both TCP and UDP within the same rule. But for some routers it is sometimes better to set each of TCP and UDP as separate port forward rules for the same port.

Did you try setting up a virtual server rule?

Hi,
Yes, I did and I also changed WSHR's settings from UPnP to manual port forwarding when I did that. I didn't create 2 separate rules for TCP and UDP as the option enabled me to set the rule for both protocols. My uTorrent is set on UPnP and is running just fine...no issues....
What baffles me is the fact that I disabled both the router's firewall as well as Window's and yet WSHR was still showing behind a firewall....unless it has something to do with the ISP's equipment...I don't know what could cause this. I'm 100% sure the ISP is not blocking the network because if it did, I wouldn't have been able to connect at all...