TinyWall is blocking VPN despite it being on whitelist

Hi guys.

 

I'm trying to use TinyWall on a Windows 7 machine to configure my Windows Firewall to block all incoming and outgoing connections aside from my browser and my VPN. I've added the main executables for both programs to my whitelist and found that, after adding my VPN's main .exe and turning TW on, my connection drops as my VPN cannot connect to the server. I think what this might mean is that my VPN depends on more executables being whitelisted than just the main one, but I cannot figure out which ones to add to the whitelist.

 

Is anyone able to give any advice?

Edited by hamluis, 28 August 2017 - 02:33 PM.
Moved from Win 7 to Firewalls - Hamluis.

Manage -> Special Exceptions [ VPN PPTP / L2TP IPSEC ] check and re-try

Is tinywall a trustworthy software?

Manage -> Special Exceptions [ VPN PPTP / L2TP IPSEC ] check and re-try

 

Thanks for your reply.

 

Unfortunately this does not work.

I seem to have the problem under control - I enabled 'autolean' and found that one of the .exes in my VPN's folder allowed me to browse the internet, which was strange, because I'm sure I had previously added all of them to the exception list and it still did not work. While I can browse the internet now with TinyWall on, SpyBot seems to have access to the internet to update, despite it not being on TW's exceptions list.

I had this same issue, and while this was a ready solution, it did mean that a bunch of things connected that I had previously forbade... Oh, the notifications!

 

In reviewing my TinyWall 'Application Exceptions', the ProtonVPN exe files that 'autolearn' collected are listed here. To test this, I just reconnected without an issue, with I had previously been loathe to do, as dropping a successful ProtonVPN connection has always previously resulted in it hanging on 'assigning IP'

 

Note: in the exception 'Type' they were listed as Executable and Service. This is copied from the 'Application' field.

 

Excecutable

• C:\Program Files\Proton\VPN\v3.1.0\ProtonVPN.exe
• C:\Program Files\Proton\VPN\v3.1.0\ProtonVPNService.exe
• C:\Program Files\Proton\VPN\v3.1.0\Resources\openvpn.exe

Service

• ProtonVPN Service (C:\Program Files\Proton\VPN\v3.1.0\ProtonVPNService.exe)

I hope this helps someone.

Hello and welcome to BC, @Elstrom:

You wrote:

I had this same issue, and while this was a ready solution, it did mean that a bunch of things connected that I had previously forbade... Oh, the notifications!
 
In reviewing my TinyWall 'Application Exceptions', the ProtonVPN exe files that 'autolearn' collected are listed here. To test this, I just reconnected without an issue, with I had previously been loathe to do, as dropping a successful ProtonVPN connection has always previously resulted in it hanging on 'assigning IP'
 
Note: in the exception 'Type' they were listed as Executable and Service. This is copied from the 'Application' field.
 
Excecutable

• C:\Program Files\Proton\VPN\v3.1.0\ProtonVPN.exe
• C:\Program Files\Proton\VPN\v3.1.0\ProtonVPNService.exe
• C:\Program Files\Proton\VPN\v3.1.0\Resources\openvpn.exe

Service

• ProtonVPN Service (C:\Program Files\Proton\VPN\v3.1.0\ProtonVPNService.exe)

I hope this helps someone.

Thanks for the suggestions.
Did you notice that the Topic Starter reported solving his problem back in September 2017?

Much will have likely changed with both the software and the OS platforms since then.
And it's a good bet he may no longer be following this old thread.

Friendly suggestion: please take a look at the date of the thread before posting. ;-)

Thanks

Typo edit

Edited by MoxieMomma, 26 August 2023 - 06:53 AM.