# 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](https://kb.filewave.com/books/filewave-server/page/filewave-server-should-not-have-ipv6-enabled "FileWave Server should not have IPv6 enabled") for the best experience. ## Port Testing Please consider downloading the [FileWave Port Testing](https://supportresources.filewave.com) 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](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 the defined port, check the Port setting in FileWave Central > Preferences > Mobile > MDM Server > Port

**Server Ports****Service****Protocol****Server In/Out****Description**
80HTTPTCPOutgoingFileWave Software Updates (apple.com & microsoft.com) \*\*\*
443HTTPSTCPOutgoingFileWave 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)
443HTTPSTCPIncomingFileWave Anywhere API endpoints - [Anywhere API (v2 API)](https://kb.filewave.com/books/application-programming-interface-api/page/filewave-anywhere-api-v2 "Anywhere API (v2 API)")
20015ProprietaryTCPIncomingFileWave Client to Server; Legacy but should be used as the port by the Agent. SSL traffic will run on 20017. (Server does not listen to this port in FileWave 15.4+)
20016SSLTCPIncomingFileWave Central to Server
20017SSLTCPIncomingFileWave Client to Server: Secure
20019SSLTCPIncomingBooster to Server: Priority Traffic
20022SSL\*\*TCPIncomingFileWave Central to Server: NATS FileWave Client to Server: NATS IVS to Server: NATS
20023SSL\*\*TCPIncomingFileWave Booster to Server: NATS
20124SSLTCPIncomingFileWave Server JSON Websockets (JWT) Websocket connections for NATS SERVER used between FW Anywhere and FW Server. (Added 14.10.0)
20441ProprietaryTCPIncomingFileWave Client to Server: Remote Client Monitor
20443HTTPSTCPIncomingFileWave Client to Server: Profiles Booster to Server: Inventory/Discovery API endpoints - [Command Line API (v1)](https://kb.filewave.com/books/application-programming-interface-api/page/command-line-api-v1 "Command Line API (v1)")
20445HTTPSTCPIncomingFileWave Client to Server: Inventory Booster to Server: Inventory/Discovery API endpoints - [Command Line API (v1)](https://kb.filewave.com/books/application-programming-interface-api/page/command-line-api-v1 "Command Line API (v1)")
20446HTTPSTCPIncomingFileWave 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.*

Configuring port 20015 automatically configures port 20017(SSL)\[port entered +2\]. 20017 took priority if available. **Do not configure Client/Booster to use port 20017**. 20015 is now deprecated and 20017 will be used where 20015 is set.

## FileWave Client Ports
**Client Ports****Service****Protocol****In/Out****Description**
443HTTPSTCPOutFileWave Kiosk ( \*.filewave.cloud )
20010ProprietaryTCPInFileWave Central to Client: Client Monitor: macOS, Windows & Android APK
[![image.png](https://kb.filewave.com/uploads/images/gallery/2024-01/scaled-1680-/uDNmvTd0XYnMFNDK-image.png)](https://kb.filewave.com/uploads/images/gallery/2024-01/uDNmvTd0XYnMFNDK-image.png) ## FileWave Booster Ports
**Booster Ports****Service****Protocol****Server In/Out****Description**
20013ProprietaryTCPIncomingFileWave Client to Booster; legacy (Booster does not listen to this port in FileWave 15.4+)
20014SSLTCPIncomingFileWave Client to Booster: Secure (Booster Priority fallback)
20018SSLTCPIncomingBooster to Booster: Priority Traffic
20026SSL *†*†TCPIncomingFileWave 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

Configuring port 20013 automatically configures port 20014(SSL) \[port entered +1\]. 20014 took priority if available. **Do not configure Client/Booster to use port 20014**. 20013 is now deprecated and 20014 will be used where 20013 is set.

[![image.png](https://kb.filewave.com/uploads/images/gallery/2024-01/scaled-1680-/nJiuROmBUacku2sE-image.png)](https://kb.filewave.com/uploads/images/gallery/2024-01/nJiuROmBUacku2sE-image.png) ## Apple MDM Ports
**Apple MDM Ports****Service****Protocol****Server In/Out****Description**
443HTTPSTCPOutgoingFileWave 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)
5223APNSTCPOutgoingFileWave Server to Apple's servers (17.0.0.0/8)
20443HTTPSTCPIncomingDevice to Server: Profiles & MDM
20445HTTPSTCPIncomingFileWave Central to Server
[![image.png](https://kb.filewave.com/uploads/images/gallery/2024-01/scaled-1680-/6sr5AGcIgYhlyqfj-image.png)](https://kb.filewave.com/uploads/images/gallery/2024-01/6sr5AGcIgYhlyqfj-image.png) ## Android EMM Ports
**Android EMM Ports****Service****Protocol****Server In/Out****Description**
443HTTPSTCPOutgoingServer to EMM commands (androidmanagement.googleapis.com) Device to Activation servers (\*.clients.google.com) Device to Play Store (play.google.com) EMM commands (androidmanagement.googleapis.com) FileWave Central to Play Store (play.google.com)
20016SSLTCPIncomingFileWave Central to Server
20445HTTPSTCPIncomingFileWave Central to Server: Inventory Companion App to Server: Location Tracking
[![image.png](https://kb.filewave.com/uploads/images/gallery/2024-01/scaled-1680-/Khge6bXjb6cMtguT-image.png)](https://kb.filewave.com/uploads/images/gallery/2024-01/Khge6bXjb6cMtguT-image.png) ## Chromebook Ports
**Chromebook Ports****Service****Protocol****Server In/Out****Description**
443HTTPSTCPOutgoingServer to Chrome API Chromebook to Chrome API (www.googleapis.com)
20016SSLTCPIncomingFileWave Central to Server
20445HTTPSTCPIncomingFileWave Central to Server Chromebook Inventory Extension to Server
[![image.png](https://kb.filewave.com/uploads/images/gallery/2024-01/scaled-1680-/ICpgTIhEQx6NiMuX-image.png)](https://kb.filewave.com/uploads/images/gallery/2024-01/ICpgTIhEQx6NiMuX-image.png) ## Windows MDM Ports
**Windows MDM Ports****Service****Protocol****Server In/Out****Description**
443HTTPSTCPIncomingDevice to Server (Enrollment URL)
443HTTPSTCPOutgoingServer to Windows MDM (\*.azure.com) Device to Windows MDM (\*.azure.com)

NOTE: The FileWave client will also be installed and all previously listed FileWave client ports are required.

[![image.png](https://kb.filewave.com/uploads/images/gallery/2024-01/scaled-1680-/afsudCOM7XCyO5qr-image.png)](https://kb.filewave.com/uploads/images/gallery/2024-01/afsudCOM7XCyO5qr-image.png) ## FileWave IVS Ports
**IVS (Imaging) Ports****Service****Protocol****Server In/Out****Description**
67DHCPUDP Client to IVS‡‡
69TFTPUDP Client to IVS‡‡
80HTTPTCP Client to IVS
111NFSTCP/UDP Client to IVS‡
4011DHCPTCP/UDP Client to IVS: UEFI PXE‡
2049NFSTCP/UDP Client to IVS‡
20015ProprietaryTCPIncomingIVS to Server (Removed in FileWave 15.4+)
20016SSLTCPIncomingIVS to Server
20017SSLTCPIncomingIVS to Server: Secure
20022SSLTCPIncomingImaging Server to FileWave Server NATS
20443HTTPSTCPIncomingIVS to Server: Inventory
20444HTTPSTCPIncomingServer to IVS Client to IVS FileWave Anywhere interface (Appliance only)
20445HTTPSTCPIncomingIVS to Server: Inventory
*‡* *TCP/IP & UDP ‡‡ UDP only*