---
title: "Virus Checker Exceptions for Lasernet Keep"
slug: "virus-checker-exceptions"
description: "Exceptions configuration for any installed virus checker to limit interference with Lasernet Keep operations."
tags: ["Configuration", "Lasernet Keep", "Virus checker"]
updated: 2026-05-27T14:49:25Z
published: 2026-05-27T14:49:25Z
canonical: "kb.lasernetgroup.com/virus-checker-exceptions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Virus Checker Exceptions for Lasernet Keep

This article describes the virus‑checker exception settings to prevent interference with Lasernet Keep operations.

## Folders

Anti-virus software must ignore the following folders:

| **Purpose** | **Location** | **Example** |
| --- | --- | --- |
| Installation folder | As installed | - Keep 11.1 and later: `C:\Program Files\Lasernet\Lasernet Keep\Server_11.<minor version> - <node name>` - Keep 11.0: `C:\Program Files\Formpipe Software\Lasernet Keep\Server_11.0 - <node name>` Appropriately substitute `<minor version>` and `<node name>`. |
| Archive folder | Configured in **Server Settings** | `C:\archive` |
| Chunks folder | Usually within **archive** folder | `C:\archive\chunks` |
| Temp folder | Default Windows folder | `C:\Windows\Temp` |

## Ports (Standalone Installations)

Standalone installations of Keep connect to services using the listed ports.

| **Purpose** | **Location** | **Example** |
| --- | --- | --- |
| HTTPS | Incoming | `443` |
| HTTP management | Incoming | `9990` |
| Database connection | Outgoing | `1433` |
| SMTP (if emailing is configured) | Outgoing | `25` |
| Secure SMTP (if emailing is configured) | Outgoing | `465`, `587` |
| LDAP server | Outgoing | `389` |
| LDAPS server | Outgoing | `636` |

## Ports (Clustered Installations)

The following sections list the default port bindings for each node type in a cluster, along with the interfaces they use.

For example, for Keep, the HTTP port is affected by the port offset and uses the wildcard interface, which, by default, is the IPv4 wildcard `0.0.0.0`.

Refer to the server logs to see which ports and bindings are in use. At server start up, messages similar to the following are displayed on the console: `HTTP listener default listening on 0.0.0.0:8180`

### Database Server

Ensure the listed default ports are open for inbound connections.

| **Server type** | **Default port** |
| --- | --- |
| MS SQL server | `1433` |
| Oracle | `1521` |

### PDC / SDC

The primary or secondary domain controllers use the following interfaces and ports.

#### Interfaces / Interface Selection

- **Management**
  - Default interface: `0.0.0.0` (IPv4 wildcard).
  - Overridden by: `jboss.bind.address.management`.
- **Public**
  - Default interface: Any network interface that satisfies *all* of the following criteria:
    - Supports multicast.
    - Is up and configured.
    - Is NOT the loopback interface.
- **Wildcard**
  - Default interface: `0.0.0.0` (IPv4 wildcard).
- **Multicast**
  - The multicast address chosen during installation.

#### Ports

| **Purpose** | **Wildfly interface** | **Default port** | **Protocol** | **Overridden by** | **Obeys port offset?** |
| --- | --- | --- | --- | --- | --- |
| HTTP management | management | `19990` | TCP | `jboss.management.http.port` | ✘ |
| Native management | management | `19999` | TCP | `jboss.management.native.port` | ✘ |
| HTTP | wildcard | `8080` | TCP | `jboss.http.port` | ✔ |
| HTTPS | wildcard | `8443` | TCP | `jboss.https.port` | ✔ |
| mcmp-management | public | `8090` | TCP | `jboss.mcmp.port` | ✔ |
| modcluster | multicast | `23364` | **UDP** | – | ✘ |

### Keep Server

The Keep server uses the following interfaces and ports:

#### Interfaces / Interface Selection

- **Management**
  - Default interface: `127.0.0.1` (IPv4 loopback).
  - Overridden by: `jboss.bind.address.management`.
- **Public**
  - Default interface: Any network interface that satisfies *all* of the following criteria::
    - Supports multicast.
    - Is up and configured.
    - Is NOT the loopback interface.
- **Wildcard**
  - Default interface: `0.0.0.0` (IPv4 wildcard).
- **Private**
  - Default interface: `127.0.0.1` (IPv4 loopback).
  - Overridden by: `jboss.bind.address.private`.
- **Unsecure**
  - Default interface: 127.0.0.1 (IPv4 loopback).
  - Overridden by: `jboss.bind.address.unsecure`.
- **Multicast**
  - The multicast address chosen during installation.

#### Ports

| **Purpose** | **Wildfly interface** | **Default port** | **Protocol** | **Overridden by** | **Obeys port offset?** |
| --- | --- | --- | --- | --- | --- |
| HTTP Management | management | 19990 | TCP | `jboss.management.http.port` | ✘ |
| Native Management | management | 19999 | TCP | `jboss.management.native.port` | ✘ |
| HTTP | wildcard | 8080 | TCP | `jboss.http.port` | ✔ |
| HTTPS | wildcard | 8443 | TCP | `jboss.https.port` | ✔ |
| ajp | public | 8009 | TCP | `jboss.ajp.port` | ✔ |
| jgroups-udp | public | 55200 | **UDP** | – | ✔ |
| multicast | 45688 | **UDP** | – | ✘ |
| modcluster | multicast | 23364 | **UDP** | – | ✘ |
| jgroups-udp failure-detection | private | 54200 | **UDP** | – | ✔ |
| iiop | unsecure | 3528 | TCP | – | ✔ |
| iiop-ssl | unsecure | 3529 | TCP | – | ✔ |