Posted  by  admin

Vipre Update File Download


Licensing

Update
Domain
Protocol
WANlicensing.viprebusiness.com443HTTP over TLSLicensing communication

Definition Updates

Domain
Protocol
WANupdates.sunbeltsoftware.com80HTTPVIPRE definitions
WANbdefs.threattrack.com80HTTPVIPRE Beetle definitions
WANmap2.hwcdn.net80HTTPVIPRE Beetle definitions
LANVSS8123HTTPVSS hosting VIPRE Beetle definitions for 9.3 - 10.x Agents
LANVSS8125HTTP over TLSVSS hosing VIPRE Beetle definitions for 11.0 and above Windows Agents

Agent Installs

Domain
Protocol
LANVSS135dcom-scmWMI Push Installation
LANVSS139 & 445netbios-ssn & microsoft-dsSMB Push Installation (legacy fallback)
LANVSS389ldapAutomatic Agent Installation using AD Queries to obtain machine/host names

VIPRE Removal Tool is meant to remove VIPRE antivirus products from your machine when other methods fail. VIPRE Removal Tool features a straightforward interface that will guide you through the simple 2-step removal process. After the tool is run and VIPRE products are located and deleted, you will be required to restart your machine. Vipre Definition Files November 23, 2021 download page. Vipre Definition Files Size: 328Mb. Downloaded: 12,257 times. VIPRE Internet Security Pro Free Download is the award-winning malware defense application that includes a two-way firewall, spam filter and evil website. Download the latest version of Vipre Antivirus for Windows. Low resource comsumption antivirus. Vipre Antivirus is a safety application thought to be used.

Software Updates

Domain
Protocol
WAN80HTTPWindows, Hyper-V (Installer), and Mac agents. All other supplemental packages
LANVSS80HTTPAgent Installation Port (default port when not in use by another process)

Agent Communication

Domain
Protocol
WANapps.viprebusiness.com443HTTP over TLSWindows roaming agents
WANbusiness.vipremobile.com443HTTP over TLSiOS and Android agents
LANVSS18082/18086SOAPWindows agents VIPRE definitions, events, policy updates
LANVSS18090SOAPHyper-V agents

Systems and other Backend service connections

Vipre Update File Downloads

Domain
Protocol
WANftp.threattrack.com21FTPDiagnostics - Submit logs to VIPRE support
WANsupport.threattracksecurity.com80 & 443HTTP and HTTP over TLSDiagnostics - Instructions to manually submit
WANwww.sunbeltsoftware.com80HTTPMessage of the Day (MOTD)
WANec.threattrack.com80HTTPPatch Management products
LANVSS18088Remote Console connections
LANUser-defined25SMTPEmail alerts and emailed reports
LANUnprotected Computer Discovery
WANlicensing.viprebusiness.com443HTTP over TLS

Email alerts*, Weekly Report*, and Telemetry

*When SMTP email server is not defined

LANVSS1433ms-sql-sSQL Server connections (if configured)
LANVSS/Agent445microsoft-dsStart Agents

Links

Domain
Protocol
WAN

go.vipre.com

443HTTP over TLSBuy Now
WANdefinitions.threattrack.com80HTTPView the version status page within Site Properties and Help About page
WANwww.sunbeltsecurity.com80HTTPResearch Center
WANgo.threattracksecurity.com / www.vipre.com80 / 443HTTP / HTTP over TLSSupport
WANsuccess.vipre.com443HTTP over TLSInstall Existing Agent Information, Message of the Day (MOTD) links
WAN443HTTP over TLSMessage of the Day (MOTD) links
WANwww.vipre.com443HTTP over TLSEULA


VES Agent Communication

DirectionPortSource / DestinationDescriptionAgents
Outbound18082 (soap)

Management Console (VSS)

Responsible for a VIPRE Agent's heartbeat to the VIPRE ConsoleWindows Agents
Inbound18086 (soap)Allows notifications of pending Deferred Work from the VIPRE Console
Any

135

Allows WMI (Windows Management Instrumentation) updates

  • Primary connection method for agent push installation
  • Note: Auto Deployment will fail unless these ports are excluded
Inbound1024-65535WMI dynamic ports for agent push installation
Any139, 445

Allows Microsoft File & Printer Sharing traffic

  • Start agent(s) from Console
  • Backup connection method for agent push installations
    • Only used if primary method method fails
    • Note: Auto Deployment will fail unless these ports are excluded
Outbound443 (https)apps.viprebusiness.comCommunication to Management Console via Roaming ServiceWindows Roaming Agents
  • Note: Non-Proxy connection required for installation

Definition Updates

Port
Description

Outbound

80 (http)updates.sunbeltsoftware.comVIPRE definition updates (via Internet connection)

Windows Roaming Agent
Windows Agents configured to use VIPRE Security Update Servers
Android agent
Mac agent

Outbound

80 (http)

VIPRE definition updates (via Internet connection)

Windows Roaming Agent
Windows Agents configured to use VIPRE Security Update Servers
Hyper-V agent
Android agent
Mac agent

Outbound18082 (soap)Management Console (VSS)VIPRE definition updatesWindows agent
Outboud18090 (soap)Management Console (VSS)VIPRE definition updatesHyper-V agent
Outbound8123 (http)Management Console (VSS)

Responsible for a VIPRE Agent's definitions and patch management updates from the VIPRE Console (VES Agent v10.1 and below)

Windows agent
Outbound8125 (https)Management Console (VSS)Responsible for a VIPRE Agent's definitions from the VIPRE Console (VES Agent v11.0 and above)Windows agent

Cloud Servers (Antimalware, antiphishing and content control scanning)

Port
Description
Outbound443 (https)nimbus.bitdefender.netBitdefender Cloud Servers
Outbound80 (http), 443 (https)nis.ng.vipre.comVIPRE Cloud Servers
Outbound80 (http), 443 (https)sink.ng.vipre.comVIPRE Web protection sinkhole
Outbound443 (https)clients2.google.comVIPRE Chrome Extension
Outbound443 (https)go.vipre.comVIPRE Firefox Extension Install
Outbound443 (https)addons.mozilla.orgVIPRE Firefox Extension Install
Outbound80 (http)ec.threattrack.comPatch Management

Patch Management Network Traffic

Port
Description
Outbound 80 (http) / 443 (https)3rd Party Vendor(s)

Access to download directly from vendor of missing patch (VES Agent v11.0 and above)

Diagnostics

Port
Description

Outbound

21 (ftp)ftp.threattrack.comPort used for submitting endpoint diagnostic logs.

Web Links

Port
Description

Outbound

80 (http), 443 (https)vipre.comVIPRE Home Page, EULA and Privacy Policy

TBD (VipreAAPSvc.exe) Network Traffic

Port
Description

Outbound

443 (https)

(151.139.128.14)

Highwinds Network Group
Latest

TBD (VipreAAPSvc.exe) Network Traffic

Port
Description
Outbound 80 (http)

(117.18.237.29)

inetnum: 117.18.232.0 - 117.18.239.255
netname: EDGECAST-APAC
descr: EdgeCast Networks Asia Pacific Network


Vipre Update File Download Not Working


Cloud-site Connection

DirectionPortSource / DestinationDescription
Outbound18082 (soap)

*.myvipre.com

VIPRE Cloud-site Agent Communication
80 (http), 443 (https)

VIPRE Cloud-site Web Console

(Access to Cloud-site Web Console redirect to 443 )

Definition Updates

Port
Description

Outbound

80 (http)updates.sunbeltsoftware.comVIPRE definition updates (e.g. Manifest)

Outbound

80 (http)

bdefs.threattrack.com

hw.threattrack.com

VIPRE definition updates (Highwinds CDN)

Definition Updates via VIPRE Update Proxy (local update proxy)

Port
Description

Outbound

18085 (http)VIPRE Update Proxy server

VIPRE definition updates via local VIPRE Update Proxy server (VES Agent v11.0 and above)

  • Note: VIPRE Update Proxy Overview

Cloud Servers (Antimalware, antiphishing and content control scanning)

Port
Description
Outbound443 (https)nimbus.bitdefender.netBitdefender Cloud Servers
Outbound80 (http), 443 (https)nis.ng.vipre.comVIPRE Cloud Servers
Outbound80 (http), 443 (https)sink.ng.vipre.comVIPRE Web protection sinkhole
Outbound443 (https)clients2.google.comVIPRE Chrome Extension
Outbound443 (https)go.vipre.comVIPRE Firefox Extension Install
Outbound443 (https)addons.mozilla.orgVIPRE Firefox Extension Install

Diagnostics

Port
Description

Outbound

21 (ftp)ftp.threattrack.comPort used for submitting endpoint diagnostic logs.

Web Links

Port
Description

Outbound

80 (http), 443 (https)vipre.comVIPRE Home Page, EULA and Privacy Policy

(VipreAAPSvc.exe) Network Traffic

Port
Description

Outbound

443 (https)

ocsp.usertrust.com

(MicroInstaller.exe) Network Traffic

Port
Description
Outbound 80 (http)

ocsp.digicert.com

ocsp.sca1b.amazontrust.com

crl.sca1b.amazontrust.com

*OCSP Servers

Certificate Revocation Status Check

Icon

If Cloud Agent MicroInstaller is unable to push through with installation and logging this error it's log file:

  • SBECommunicationLib ATL::CSoapWininetClient::SendRequest: Error 12057 while trying SendRequest.

The underlying issue with this error is that a machine is being blocked from contacting the revocation servers, adding the *OCSP servers listed above to firewall or proxy whitelist should solve the issue.


Cloud-site Connection

Port
Description
Outbound18083

mac.myvipre.com

VIPRE Cloud-site Agent Communication
Outbound80 (http), 443 (https)*.myvipre.com

VIPRE Cloud-site Web Console

(Access to Cloud-site Web Console redirect to 443 )

Software and Definition Updates

Port
Description

Outbound

80 (http)

bdefs.threattrack.com

hw.threattrack.com

VIPRE software and definition updates (Highwinds CDN)

Web Links

Port
Description

Outbound

80 (http), 443 (https)vipre.comAccess to EULA and Privacy Policy
Outbound80 (http), 443 (https)

success.vipre.com

VIPRE Online Help and Support Documents

(Installer) Network Traffic

Port
Description
Outbound 80 (http)

This article covers hardware, software, and network prerequisites. Then it steps you through installing the software, adding a firewall rule, and updating your VIPRE Cloud policies to use the new proxy.

The four steps to install and configure VIPRE Update Proxy are as follows:

Additionally, you may choose to uninstall VIPRE Update Proxy.

Step 1: Perform prerequisite checks

To run VIPRE Update Proxy effectively, you need

Hardware / Software

  • A PC with a network connection
  • Any Desktop or Server version of Windows
  • Microsoft .NET Framework 4.0 or higher

Network prerequisites

The chosen host machine should

  • have a static IP address
  • be on the same internal network as your VIPRE Cloud agents
  • be reachable by your VIPRE Cloud agents across the internal network
  • use a firewall to restrict access to only
    • the VIPRE Update Proxy port you choose
    • local networks with VIPRE Cloud agents that require updates
  • be able to access these internet hosts and download these file types

Additionally, the host machine should not

  • be connected to external or public networks

Step 2: Install VIPRE Update Proxy

Installation is quick and simple. It is also displayed in the Introduction to VIPRE Update Proxy video.

VIPRE Update Proxy (1.4MB .exe)

  1. Download the VIPRE Update Proxy installer (above) to your host machine, and launch it
  2. Select an installation directory and click Next
  3. Choose an unused port for VIPRE Update Proxy to listen on, and click Next.
    We recommend choosing an unused port instead of the default (18085), as it is the default port for Nginx.
  4. Choose a local directory for VIPRE Update Proxy to use for the cache, and click Install.
    The software installs VIPRE Update Proxy and sets it to start as a system service
  5. When installation is complete, click Finish.
    The VIPRE Update Proxy installer opens the default web browser and performs two tests (Installation and Connection).
  6. Once the tests finish, verify the messages below are displayed to indicate the tests were successful
  • Installation - The update proxy software installation and service registration succeeded, and the proxy is now running on the port you selected. This should always succeed – If the install process encounters any issues, it will notify you before this point.
  • Connection - The update proxy succeeded in caching a small, remote test file. If the test cannot reach the VIPRE content servers in a given test period, it will fail.

If the connection test fails, check that your host can reach the necessary update servers and download required file types, then click Check Now to test again after making any changes.

The update proxy runs under Windows Services as “VIPRE Update Proxy” and is set to start automatically on boot.

Step 3: Create and test a new firewall rule

On the host, create a firewall rule which allows inbound traffic on the specified port to the proxy executable. Ensure your rule allows only required domains or connections from your local network.

Below is a sample Windows 7 firewall rule.

  • Rule type: Inbound / Program
  • Program path: /Program Files (x86)/VIPRE Update Proxy/nginx/nginx.exe
  • Action: Allow the connection
  • Profile: (This is specific to your setup. Select whichever options allow only the required connections.)
  • Name: Give the rule a name and optional description

Test the firewall rule by pointing a web browser from a different host to VIPRE Update Proxy. (e.g. http://PROXYHOST:18085/vup/index.html)

Avg Update File

In this example, replace PROXYHOST with the hostname or IP of your host machine and replace 18085 with the port you selected during install.

  • If successful, you will see the VIPRE Update Proxy confirmation page (above)
  • If unsuccessful, check the following:
    • Confirm that you have entered the hostname or IP address correctly
    • Confirm that the port number specified in the URL matches the port specified during the install of VIPRE Update Proxy
    • Confirm your firewall rule on the host is correct
    • If you’re still having problems, disable the firewall rule and/or re-install the proxy to confirm you can connect to the host from your test machine without any additional settings in place

Step 4: Update your VIPRE Cloud policies

Agent update proxy settings are configured at the policy level in VIPRE Cloud.

Because all agents on a policy use the same update settings, agents should be segregated by policy. For example, you may wish to use a policy to group agents by a specific subnet, or at a branch office location.

Configure a policy to use VIPRE Update Proxy

  1. In VIPRE Cloud, navigate to Policies > Edit policy > Agent > Updates & Communication
  2. Under Update Communications, select Use a local update server
  3. Enter the VIPRE Update Proxy host location (e.g. http://10.32.10.136:18085 )
  4. In the top right, select Save

Vipre Update File Download

Policy changes are picked up by each agent the next time they sync with the Cloud console (usually within a minute or so).

Vipre Antivirus Update File Free Download

You're done! Your VIPRE Cloud agents will now use VIPRE Update Proxy on your local host.

Uninstall VIPRE Update Proxy

When uninstalling VIPRE Update Proxy from the proxy host, you should perform the following steps:

Vipre Update File Download Free

Step 1 - Configure your policies to no longer use VIPRE Update Proxy

  1. In VIPRE Cloud, navigate to Policies > Edit policy > Agent > Updates & Communication
  2. Under Update Communications, deselect Use a local update server
  3. In the top right, select Save

Repeat steps 1–3 for every policy that uses VIPRE Update Proxy.

Policy changes are picked up by each agent the next time they sync with the Cloud console (usually within a minute or so).

Vipre Antivirus Premium Update File Download

Step 2 - Uninstall VIPRE Update Proxy from the proxy host

  1. Log on to the proxy host machine
  2. Uninstall VIPRE Update Proxy using Windows Add/Remove Programs functionality