![]() Out of a few hundred users I'm the only one using TinyWall, and none of the other users experience a ping-timeout with either Windows or a 3rd-party firewall. Without that intermittent ping from my system, there will be a ping-timeout and the session is terminated. ![]() The Blue Ridge Networks server doesn't ping my system, it is my system that has to ping the OpenVPN server for the current VPN session to remain active. With TinyWall uninstalled everything is fine - OpenVPN works with it installed OpenVPN gets a ping-timeout. Disabling TinyWall also does not fix the issue. Create an exception rule for System(0) and that rule does not work. TinyWall blocks ICMPv4 Out for System(0) to the OpenVPN website. The bottom line is that TinyWall causes a ping-timeout and nothing will fix it - using Learning Mode, creating unrestricted in\out-bound firewall rules for OpenVPN, etc. Oct 29th, 2021 at 3:00 PM Well right off the bat, Netextender and Sonicwall Mobile Connect are sonicwalls free VPN clients. AppGuard is not the problem - since the OpenVPN is part of AppGuard Enterprise. there is also an option to kill leading me to believe these ports are open and. ![]() Yet, if I right click on any of the ports, there is an option for UnBlock. Using Enterprise configured OpenVPN with split-tunneling to a private IP\subnet. I see under Show Connections if I have Open Ports checked, I get a list of what I presume to be, Open ports (open meaning unblocked IMO). TW 2.1.8 will block Windows Mail App after Learning and then enabling Normal mode. Usually, when i uninstall a program, TW will highlight the uninstalled program firewall rule and add a red X to indicate that the program is missing. If I uninstall both the Windows Phone and Companion Phone Apps, then TW auto-deletes the Phone App firewall rule while the Companion Phone App rule remains. Trying to track these down these type of block events without some sort of log is needlessly time consuming - and, consequently - really annoying. The way TW works now, a user will probably miss at least a few programs that connect out - for example, wermgr.exe, MRT.exe, etc. TinyWall needs a plain text log of block events. I have noticed when rebooting the system or upon waking a system from sleep - that the network is unavailable (yellow triangle with exclamation mark) for 10 or 15 seconds or so after the TW tray icon appears.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |