Default TCP and UDP Port Usage

FileWave software uses the below-listed TCP/IP ports. These are default settings and may be configured to listen on different ports if required. Consider FileWave Server should not have IPv6 enabled for the best experience.

Port Testing

Please consider downloading the FileWave Port Testing macOS/Windows utility to confirm communication of Google Cloud Messaging, Apple Push Notifications and connectivity between device network(s) and Server/Boosters.

The following may be run from the server to confirm Apple, Microsoft, and FileWave services:

Server Command Line

sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc check_connections

TeamViewer Ports

TeamViewer has an additional set of ports to consider:

https://community.teamviewer.com/English/kb/articles/4139-ports-used-by-teamviewer

FileWave Server Ports

MDM default port is now 20445 as shown throughout this KB. On older versions of FileWave, this was 20443. To confirm defined port, check the Port setting in FileWave Central > Preferences > Mobile > MDM Server > Port

Server Ports Service Protocol Server In/Out Description
80 HTTP TCP Outgoing

FileWave Software Updates (apple.com & microsoft.com) ***

443 HTTPS TCP Outgoing FileWave License Server (fwks.filewave.com & logstash.filewave.com)

FileWave Software Updates (apple.com) ***

FileWave/TeamViewer Session Server (rcs.filewave.com)

FileWave/TeamViewer Push Notification Server (fwpn.filewave.com)

443 HTTPS TCP Incoming FileWave Anywhere
API endpoints - Anywhere API (v2 API)
20015 Proprietary TCP Incoming FileWave Client to Server; Legacy but should be used as the port by the Agent. SSL traffic will run on 20017.
20016 SSL TCP Incoming FileWave Central to Server
20017 SSL TCP Incoming FileWave Client to Server: Secure (used after connecting on 20015)
20019 SSL TCP Incoming Booster to Server: Priority Traffic
20022 SSL** TCP Incoming FileWave Central to Server: NATS

 

FileWave Client to Server: NATS

IVS to Server: NATS

20023 SSL** TCP Incoming FileWave Booster to Server: NATS
20124 SSL TCP Incoming FileWave Server JSON Websockets (JWT) Websocket connections for NATS SERVER used between FW Anywhere and FW Server. (Added 14.10.0)
20441 Proprietary TCP Incoming FileWave Client to Server: Remote Client Monitor
20443 HTTPS TCP Incoming FileWave Client to Server: Profiles

Booster to Server: Inventory/Discovery
API endpoints - Command Line API (v1)

20445 HTTPS TCP Incoming FileWave Client to Server: Inventory

Booster to Server: Inventory/Discovery
API endpoints - Command Line API (v1)

20446 HTTPS TCP Incoming FileWave Central and FileWave Anywhere to Dashboard

* NATS includes: Remote Control Publishing, Remote Control Routing, device renaming, revoking device certificates, push notifications

** Only encrypted when compatibility mode is disabled

*** Also used by FileWave Central to vendor Software Update Servers.

FileWave Communication Diagram

Setting a client or booster port for server of 20015 will automatically set the SSL port as 20017 (port configured + 2)

Setting a client to booster port for 20013 will automatically set the SSL port as 20014 (port configured + 1)

Do not set the client or booster port for server as 20017 or client for booster port as 20014.

FileWave Client Ports

Client Ports Service Protocol Server In/Out Description
20010 Proprietary TCP N/A FileWave Central to Client: Client Monitor: macOS, Windows & Android APK

FileWave Client Port Diagram

image.png

FileWave Booster Ports

Booster Ports Service Protocol Server In/Out Description
20013 Proprietary TCP Incoming FileWave Client to Booster; legacy (used for configuration only)
20014 SSL TCP Incoming FileWave Client to Booster: Secure (Booster Priority fallback)
20018 SSL TCP Incoming Booster to Booster: Priority Traffic
20026 SSL TCP Incoming FileWave Client to Booster connections using NATS Server

† NATS includes: Remote Control Publishing, Remote Control Routing, device renaming, revoking device certificates, push notifications
† Only encrypted when compatibility mode is disabled

FileWave Booster Routing Port Diagram

image.png

Apple MDM Ports

Apple MDM Ports Service Protocol Server In/Out Description
443 HTTPS TCP Outgoing

FileWave Server to Apple's servers (17.0.0.0/8)

FileWave Admin to iTunes, DEP & VPP (17.0.0.0/8)

Device to iTunes, DEP & VPP (17.0.0.0/8)

5223 APNS TCP Outgoing FileWave Server to Apple's servers (17.0.0.0/8)
20443 HTTPS TCP Incoming Device to Server: Profiles & MDM
20445 HTTPS TCP Incoming FileWave Central to Server

Apple MDM Port Diagram