On-premises network infrastructure | PRA On-prem

Example firewall rules

Below are example firewall rules for use with BeyondTrust, including port numbers, descriptions, and required rules. If a B Series Appliance has multiple IP addresses, outbound traffic for services such as LDAP can flow out of any configured address. Because of this, it is best practice to make firewall rules apply for all IP addresses configured on each B Series Appliance.

Firewall Rules
Internet to the DMZ
TCP Port 80 (optional) Used to host the portal page without the user having to type HTTPS. The traffic can be automatically rolled over to port 443.
TCP Port 443 (required)\* Used for all session traffic.
UDP Port 3478 (optional) Used to enable Peer-to-Peer connections if the **Use Appliance as Peer-to-Peer Server** option is selected.
Internal Network to the DMZ
TCP Port 80 (optional) Used to host the portal page without the user having to type HTTPS. The traffic can be automatically rolled over to port 443.
TCP Port 161/UDP Used for SNMP queries via IP configuration settings in the /appliance interface.
TCP Port 443 (required)\* Used for all session traffic.
DMZ to the Internet
TCP Port 443 to the specific host **gwsupport.bomgar.com** (optional) Default port used to establish connections with BeyondTrust Technical Support for advanced troubleshooting/repairs.
TCP Port 443 to the specific host **btupdate.com** (optional) You can optionally enable access from the B Series Appliance on port 443 to this host for automatic updates, or you can apply updates manually.
DMZ to the Internal Network
UDP Port 123 Access NTP server and sync the time.
LDAP - TCP/UDP 389 (optional)‡ Access LDAP server and authenticate users.
LDAP - TCP/UDP 636 (optional)‡ Access LDAP server and authenticate users via SSL.
Syslog - UDP 514 (required for logging) Used to send syslog messages to a syslog server in the internal network. Alternatively, messages can be sent to a syslog server located within the DMZ.
Syslog - TCP Port 6514 Used to send syslog messages over TLS to a syslog server in the internal network. Alternatively, messages can be sent to a syslog server located within the DMZ. |
DNS - UDP 53 (required if DNS server is outside the DMZ) Access DNS server to verify that a DNS A record or CNAME record points to the B Series Appliance.
TCP Port 25, 465, or 587 (optional) Allows the B Series Appliance to send admin mail alerts. The port is set in SMTP configuration.
TCP Port 443 (optional) B Series Appliance to web services (e.g., HP Service Manager, BMC Remedy) for outbound events.
TCP Port 5696 Allows the B Series Appliance to access the KMIP server located in the internal network for Data at Rest Encryption.
Internal Network to Internal Network
Port 389, 636 (Active Directory), 445 (Local Account Management) Ports used for discovery and rotation of Vault accounts.

Each of the following BeyondTrust components can be configured to connect on a port other than 443: representative console, customer client, presentation attendee client, Jumpoint, connection agent.

If the LDAP server is outside of the DMZ, the BeyondTrust Connection Agent is used to authenticate users via LDAP.

Ports and firewalls

BeyondTrust solutions are designed to work transparently through firewalls, enabling a connection with any computer with internet connectivity, anywhere in the world. However, with certain highly secured networks, some configuration may be necessary.

Diagram: The remote client connects through a firewall with ports 80 and 443 open for outbound TCP traffic to the internet, then through a firewall with ports 80 and 443 open for inbound TCP traffic to the B Series Appliance. The support rep completes the connection through a firewall with ports 80 and 443 open for outbound traffic to the appliance and the remote client.
  • Ports 80 and 443 must be open for outbound TCP traffic on the remote system's and local user's firewalls. More ports may be available depending on your build. The diagram shows a typical network setup; more details can be found in B Series Appliance installation.

    ℹ️

    BeyondTrust Cloud requires use of port 443 only.

  • Internet security software such as software firewalls must not block BeyondTrust executable files from downloading. Some examples of software firewalls include McAfee Security, Norton Security, and Zone Alarm. If you do have a software firewall, you may experience some connection issues. To avoid such issues, configure your firewall settings to allow the following executables:

    • sra-scc.exe
    • sra-con.exe
    • sra-jpt.exe
    • sra-sjp.exe
    • sra.rfb.exe
    • sra-rdp.exe
    • sra-tnl.exe
    • sra-rdt.exe
    • sra-sjt.exe
    • sra-web.exe
    • sra-vpro-connection.exe
    • sra-cli.exe
  • For assistance with your firewall configuration, please contact the manufacturer of your firewall software.

  • See example firewall rules based on B Series Appliance location.

If you should still have difficulty making a connection, contact BeyondTrust Technical Support.


©2003-2026 BeyondTrust Corporation. All Rights Reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.