Search the Community
Showing results for tags 'emule windows firewall'.
Found 2 results
I discovered a simple quirk of setting up eMule (P2P) on Windows 10 that causes port forwarding to fail with AirVPN. This tip that may save others a lot of time. During setup eMule creates an inbound rule in Windows firewall that applies to private networks in scope. This makes sense if using eMule without a VPN. However, Windows treats the AirVPN as a public network. Consequently port forwarding with eMule and AirVPN will not work using the default inbound rule created during eMule setup. The solution is to edit the scope of the eMule inbound rule in Windows firewall to apply to both private and public profiles. The latter is the important one. This is simple to do: In Windows Firewall, right click on the inbound rule for eMule, select Properties, Advanced. Under Profiles check both Private and Public. I am not a security expert so feel free to chime in if this setting raises any concerns. This may also apply to earlier versions of Windows.
Hi all, nooby here. I have read & read and read! Got a decent handle on it I think. I got AirVPN working on my Samsung-Android, LOVE it! And, it is working on my desktop with a problem. In order to get a “High ID” on my eMule ed2k, and “Open” on my KAD I have to shut down my Windows Firewall. Ports are forwarded through to AirVPN as required and it works, GREAT, just no Firewall. I CAN use the firewall with AirVPN if I don’t want to use eMule. When I start “Net-Lock” of course it restarts the firewall and poof, eMule is blocked again And I have been using eMule successfully for years before getting AirVPN yesterday. I am sure many of you have conquered this problem already. I hope you will share your method. Thanks And thinks AirVPN people for an Awesome system!!! P.S. I am using Windows 7 Ultimate 64 bit