Overview

Full details of all required network/firewall rules for AppsAnywhere are detailed below.

Further information is available on AppsAnywhere Firewall Rules.xlsx and by request to AppsAnywhere Support or as part of an AppsAnywhere Implementation.

Firewall Rules

The following tables detail the connectivity required, grouped according to the origin of the network traffic.

All traffic is bi-directional

Internal Destinations should be amended to match internal servers and services.

There is no requirement to configure firewall rules on AppsAnywhere servers.

Inbound Traffic (Internal and External)

Sources

Internal Destination

Port

Usage

Client Devices

appsanywhere01.uni.edu

443 TCP

User access to AppsAnywhere (e.g. via a load balancer)

Jump Host

appsanywhere01.uni.edu

22 TCP

SSH access for administration (usually via a Windows jump host)

AppsAnywhere

appsanywhere01.uni.edu

80 TCP

Transfer of AppsAnywhere Client installers from other internal AppsAnywhere servers

Outbound Traffic (Internal)

Sources

Internal Destination

Port

Usage

AppsAnywhere

MSSQL.uni.edu

1433 TCP

Connection to your SQL database

AppsAnywhere

MSSQL.uni.edu

1434 UDP

Connection to your SQL database

AppsAnywhere

AD.uni.edu

636 TCP

Connection via LDAPS to Active Directory

AppsAnywhere

AD.uni.edu

88 UDP

Connection via Kerberos to Active Directory

AppsAnywhere

appsanywhere02.uni.edu

80 TCP

Transfer of AppsAnywhere Client installers to other internal AppsAnywhere servers

AppsAnywhere

cloudpaging.uni.edu

443 TCP

Connection to your Cloudpaging service (if applicable)

AppsAnywhere

parallels.uni.edu

443 TCP

Connection to the Parallels RAS service (if applicable)

AppsAnywhere

analytics.uni.edu

19999 TCP

Connection to the Analytics Appliance

AppsAnywhere

myfileshare.uni.edu

445 TCP

AppsAnywhere Service access to the Secure Download UNC path

Outbound Traffic (External)

Source

Port

Usage

AppsAnywhere

123 UDP

CentOS (Chrony) Time Service

AppsAnywhere

80 TCP

Icon Library and CentOS updates

AppsAnywhere

443 TCP

APIs, libraries and CentOS updates

AppsAnywhere

587 TCP

Email alerts via SMTP

External Destinations

The following table provides detailed information for all the outbound destinations that AppsAnywhere requires access to during normal operation.

Source

External Destination

Port

Usage

AppsAnywhere

0.centos.pool.ntp.org

123 UDP

CentOS Time Service

AppsAnywhere

1.centos.pool.ntp.org

123 UDP

CentOS Time Service

AppsAnywhere

2.centos.pool.ntp.org

123 UDP

CentOS Time Service

AppsAnywhere

3.centos.pool.ntp.org

123 UDP

CentOS Time Service

AppsAnywhere

api.appsanywhere.com

80 TCP

Icon Library

AppsAnywhere

api.software2.com

443 TCP

AppsAnywhere Server Registration

AppsAnywhere

b12228822d08f4925072-e23aef5ecad0f6168507017a4f5869f1.ssl.cf3.rackcdn.com

443 TCP

AppsAnywhere Icon Library

AppsAnywhere

mirrorlist.centos.org

80 TCP

CentOS Update Repository

AppsAnywhere

cdn.remirepo.net

80 TCP

CentOS Update Repository

AppsAnywhere

mirrors.fedoraproject.org

443 TCP

CentOS Update Repository

AppsAnywhere

rpms.remirepo.net

443 TCP

CentOS Update Repository

AppsAnywhere

packages.microsoft.com

443 TCP

CentOS Update Repository

AppsAnywhere

rpm.nodesource.com ADDED 2.11

443 TCP

Node.js Update Repository

AppsAnywhere

appsanywhereresources.blob.core.windows.net

443 TCP

Appliance Configuration Console

AppsAnywhere

1bdb4cc9b0722bc205a377fabbc4511a62a47f7610ad5c7c4e62.ssl.cf3.rackcdn.com

443 TCP

Client Management

AppsAnywhere

*.s2public.blob.core.windows.net

443 TCP

Client Management

AppsAnywhere

software2-public.azureedge.net

443 TCP

Patch Management

AppsAnywhere

ajax.googleapis.com

443 TCP

jQuery & Google Fonts

AppsAnywhere

github.com

443 TCP

Other AppsAnywhere libraries

AppsAnywhere

smtp.sendgrid.net

587 TCP

Email alerts via SMTP

For Parallels RAS, please refer to AppsAnywhere Firewall Rules.xlsx