What This Port Does
Port 20017 has no official assignment from the Internet Assigned Numbers Authority (IANA). It sits in the registered ports range (1024-49151), which means anyone can request to use it, but nobody has to ask permission.
In practice, FileWave — a mobile device management (MDM) platform — uses port 20017 for SSL-encrypted client communication.1 When you configure FileWave to use port 20015 (the legacy HTTP port), it automatically uses port 20017 for the encrypted version. The system requires SSL now, so 20017 is where the actual traffic flows.
This is an unofficial, proprietary use. FileWave didn't register this port with IANA. They just picked a number and started using it.
The Registered Ports Range
Port 20017 belongs to the registered ports range: ports 1024 through 49151.
This range exists for services that want a consistent port number but aren't fundamental Internet protocols. Companies and developers can register these ports with IANA by submitting a request, but many don't bother. They just pick a number, use it, and document it.
The risk is collision: two different services picking the same port. In practice, the 48,000+ available ports in this range make collisions rare. Most conflicts happen when companies choose "memorable" numbers (like round thousands) rather than random values.
How FileWave Uses This Port
FileWave's architecture used to allow plain HTTP communication on port 20015. Modern deployments require SSL, so when you configure port 20015, the system automatically uses port 20017 (port + 2) for the encrypted channel.1
The communication protocol uses mutual TLS (mTLS), where both the FileWave client and server authenticate each other using certificates issued by FileWave's certificate authority. Clients initiate connections to check for updates, receive commands, and report status.
FileWave's documentation explicitly tells users not to manually configure port 20017 — always enter 20015 and let the system handle the SSL port automatically.
Checking What's Listening
If you want to see what's actually using port 20017 on your system:
On Linux or macOS:
On Windows:
If FileWave is running, you'll see its process. If the port is silent, nothing is using it. If you see something unexpected, you've found either malware or another application that happened to pick the same number.
Why Unassigned Ports Matter
The registered ports range is where most modern applications live. Web servers use port 80 and 443. Databases use 3306 (MySQL) and 5432 (PostgreSQL). Mail servers use 25, 587, and 465. These are all registered ports.
Port 20017 represents how the system actually works: companies build software, pick a port that seems available, document it, and ship. If enough people use that software, the port becomes "theirs" by convention, even without formal registration.
This informal system works because:
- The range is large enough (48,000+ ports) that random collisions are rare
- Most deployments are internal, where IT controls the network
- Firewalls and network policies prevent conflicts by controlling what runs where
The Internet runs on a mix of rigid standards (port 80 is HTTP) and practical anarchy (port 20017 is whatever FileWave says it is). Both matter.
Related Ports
- Port 20015 — FileWave's legacy HTTP port (deprecated, but still the configuration entry point)
- Port 20016 — FileWave's legacy HTTPS port (also deprecated)
- Port 20030 — FileWave's main HTTPS port for server administration
- Port 20443 — Alternative HTTPS port commonly used by FileWave installations
Frequently Asked Questions
Cette page vous a-t-elle été utile ?