When a device or network is trying to connect to your computer and connection cannot be established, it is likely caused by VIPRE firewall not recognizing the device, application or network that is trying to communicate to your computer therefore, blocking or preventing any access to your computer until an exception is made. this is normal behavior of the firewall doing its job. You will need to set exceptions for applications that establishes a connection and send data over the internet to allow communication.

First, make sure that it is VIPRE Firewall causing the issues by turning VIPRE Firewall Off  and try to reproduce the issue. If it works with the firewall off, proceed below. If it still does not work with firewall off, try shutting down VIPRE temporarily. If issue persist then it is not VIPRE Firewall causing issue. Check the device, settings or contact the manufacturer or software developer instead.

For VIPRE to recognize your device or network, you will need to add exceptions to your VIPRE Firewall
  1. Open the VIPRE Interface
  2. Click Manage tab > Firewall
  3. Scroll all the way down until you see Firewall Default Behaviors
  4. Change the settings to Learning Mode
  1. A notification labeled "Firewall Learning Mode" will prompt you to confirm action, place a check in the Delete custom rules, too option and click Reset button. This will erase all custom made rules and reset the firewall back to default

  1. Try to access the application, network of the device again and you will be prompted with VIPRE notification about allowing the application to communicate to your computer over the network. Click Trust Location or put a check mark under the Make A rule box and click Allow for VIPRE to make an exception.

  1. You should now be able to establish connection to your printer/scanner, application or internet. Once this is completed, you can change the firewall settings back to Standard Mode for VIPRE to apply the rule and don't have to ask your permission every time you try to access the same connection.

The best way to address a problem like this is to find out the exact path and name of the executable that is attempting to make the connections over the internet. The easiest way to find this out is by checking the properties of the shortcut file. The file path in the Target field is what you need to add to the Firewall exceptions.
  1. Open the VIPRE
  2. Click Manage tab > Firewall
  3. Scroll down until you see Firewall Protection and click Manage Rules button

  1. Click the Add App Rule button to add exceptions and enter the path you identified from the target field

  1. Select Allow for Trusted Inbound and Outbound You can do the same for Public Inbound and Outbound, but it is recommended to set this to Prompt
  2. Continue to make port exceptions if necessary by clicking the Ports tab and click Add
  3. Enter a name for the rule
  4. Click browse and navigate to the executable or paste the path to the executable in the Application field
  5. Select the Port drop down and enter the port
  6. Select the Protocol (TCP or UDP)
  7. Click OK

In order for RDP connections to function, proper exceptions need to be made in the Firewall Application and Port exceptions:
  1. Using the information from the previous section, modify the Apps rule for Svchost.exe to allow trusted connections both inbound and outbound.
  2. Make a port exception on the RDP port for this same application (C:\Windows\System32\svchosts.exe). The name can be whatever you choose, but the application must be C:\Windows\System32\svchost.exe, the Port Number must be 3389 (or whatever you have the RDP port set as), and the Protocol must be TCP.

RDP connections should work fine, If RDP connections are not working, one of the above steps was not followed correctly.