# What are "Server Messages" and why do I want them? ## What **Route server messages via boosters** sends selected FileWave Client/server messages through Boosters instead of requiring every client to communicate directly with the FileWave Server for those messages. You may see this option in [Superprefs Editor](https://kb.filewave.com/books/filewave-client/page/filewave-client-configuration-settings "Creating a Superprefs Fileset") or [Client Monitor](https://kb.filewave.com/books/filewave-client/page/filewave-client-configuration-settings "FileWave Client Configuration Settings"). [![image.png](https://kb.filewave.com/uploads/images/gallery/2023-09/scaled-1680-/ik172n6C2V55CJ9e-image.png)](https://kb.filewave.com/uploads/images/gallery/2023-09/ik172n6C2V55CJ9e-image.png) ## When/Why FileWave Clients check in with the FileWave Server on a schedule (2 minutes by default). Server messages cover the additional client/server communication that lets the client receive status, commands, and related updates. The [Default TCP and UDP Port Usage](https://kb.filewave.com/books/filewave-general-info/page/default-tcp-and-udp-port-usage "Default TCP and UDP Port Usage") article lists 20015 and 20017 for client/server communication. NATS ports also handle notifications for workflows such as initiating a TeamViewer session.

Note: The default port setting is 20015. However, SSL is now required, and the system will automatically use port 20017 instead when 20015 is entered. Do not manually set the port to 20017. Always enter 20015, and the system will handle the SSL port change for you.

## How Server messages are the communications a client needs to work with the server. If routing is enabled, publishing and routing services can send messages like the ones below through Boosters. Enable this option when Boosters should handle more of that client communication and reduce direct load on the FileWave Server. - Checkin - Fileset properties and status - Software updates - Lock / Unlock client - Kiosk categories and item info