In this tutorial we will show you how you can add an exception rule for your VPN to your Webroot firewall.Īdding a VPN Exception Rule to your Webroot Firewallġ- Open the Webroot SecureAnywhere softwareĢ- In the top right corner of the main panel window, click on the “ gear ” icon next to “ PC Security ”ģ- From the top of the window, click to open the tab labeled “ Block/Allow Files ”Ĥ- At the bottom the window, click on “ Add ”ĥ- Browse through your computer files to get to the location of where you saved your VPN application when you installed itĦ- Select the VPN application and click on “ Open ”ħ- From the list, click to select the radio button under “ Allow ” next to the VPN applicationĨ- Close the Webroot SecureAnywhere software The solution to this is notifying the Webroot that this VPN application is safe and trustworthy by adding an exception rule within the firewall settings especially for the VPN application. This is due to the Webroot firewall treating the VPN application as a threat and completely blocking it. The problem is that using a VPN with the Webroot firewall might cause a software conflict preventing the VPN from operating. Even though users might prefer the firewall created by Webroot over other names, yet when it comes to virtual private networks or VPNs, they might have other preferences. Ever since Webroot started operating and it has been continuously improving and expanding to provide both home and business consumers with all the needs when it comes to computer and internet security. In more than one review, Webroot SecureAnywhere, was rated one of the top antivirus and firewall software available in the market today.
The fact we have to provide registry entries in the first place to maintain DNS is absurd, but I don't know.Webroot is a US-based private company specializing in internet security software which was founded back in 1997. It's almost as if Webroot is IGNORING the registry entries sporadically. We've tested this on multiple machines, multiple networks, multiple versions of Cisco just to make sure it has nothing to do with their program, and nobody seems to know what's causing the issue. The only way to get them back up it seemed was to repetitiously flush the DNS and restart the DNSProxyAgent until it finally remembered the registry entries and went back to normal. Sometimes it would plague the machine itself, resulting in a DNS error when simply attempting to connect to the VPN and setting the local NICS DNS servers to 127.0.0.1, not allowing anything to be resolved and even cutting the ability for us to reach the users remotely. But it continues to randomly pop up from user to user without rhyme or reason. You could often run the script to restart the DNSProxyAgent and flush the DNS, and the user would be good again. The registry entries would still be there, but the DNS issue would reappear. Only problem is that this issue often comes back. We looped these fixes into a powershell script that you could run remotely and it would fix the issue 9/10 times. We also figured out you could add Cisco An圜onnect to the No-Loopback_VPN entry and it would have the same result We would create an Excluded-NIC-List and add the cisco adapter to it in the registry, restart the DNSProxyAgent service, flush the DNS, and everything was golden. HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\webroot\DnsAgent The "fix" that was provided to us by Webroot was a change to the registry: Disconnect from the VPN, works perfectly fine. Every webpage results in a "The IP Address could not be resolved" error code. The issue that has been occurring for about 8 months now is that whenever our remote users connect to the VPN, DNS goes out the window. For our VPN, we use the Cisco An圜onnect Secure Mobility Client. Our company utilizes the Webroot DNS Protection Agent on our machines.
Wanted to throw this out here to see if anyone had any suggestions as I am at a loss.
0 kommentar(er)
