When enabled, the Windows Firewall blocks all incoming network traffic to your computer except those applications and ports you allow. Use the Windows Firewall control panel utility to manage these exceptions.
Note: It is not necessary to disable the Windows Firewall to use our software. Firewalls provide a much higher level of security to your computer than default Windows security.
We strongly recommend that you leave the firewall in place, and use the mechanisms in the firewall to allow the traffic you need.
Firewall Program Exception
The installers for RPM Remote Print Manager® (RPM) and ExcelliPrint® create a program exception. The program exception allows the software to receive print jobs from your host system. The exception might be enabled only for specific network types. If our software is not receiving connections, and you have already established that the host system uses the correct IP address, then we recommend you review the firewall exception.
- Open the Control Panel. In Category view, click System and Security.
- Beneath Windows Defender Firewall, click Check Firewall Status.
- Determine the status of the Windows Firewall for each type of active network. Network types include Domain, Private, or Public. If the Windows Firewall is off, then it is not blocking connections from your host system. It may be a good idea to add the exception in case Windows Firewall is turned on at a later time.
- Click Allow an app or feature through Windows Defender Firewall.
- Look for the RPM Remote Print Manager or ExcelliPrint exception. Enable this exception for the active network types you noted in the previous step. You may need to click Change settings to elevate the process before you can add exceptions.
- If not found, click the"Allow another app..." button. In the "Add an App" dialog, click Browse and locate the executable you wish to allow. By default, the RPM program is RpmSrv.exe in C:\Program Files\Brooks Internet Software\RPM for RPM and C:\Program Files\Brooks Internet Software\ExcelliPrint\EPrintSrv.exe for ExcelliPrint.
- Click Add.
- Verify the program is listed in the Allowed apps and features list. Click the OK button to accept the changes and dismiss the dialog.
- Click OK on the network connection's "Properties" dialog to apply the changes.
Note: Do not make any changes to existing exceptions.
Your new firewall exceptions will take effect immediately.
Firewall Port Exceptions
Determine Ports to Allow for RPM
While this is a more involved process, you may wish to use port exceptions instead. If so, delete the auto-created program exception and follow the instructions below.
- In RPM, choose General Settings from the View menu. Click Ports.
- Note the port number for each entry in the list, especially telnet and LPD ports. Usually, this will include 515 and possibly 9100. RPC ports are used only for the service and UI to communicate with each other. You should only include RPC ports if you use the UI on a remote computer.
Determine Ports to Allow for ExcelliPrint
The software can be configured to listen on multiple TCP ports simultaneously. First, you need to determine which ports are used by your print host, then create an exception for each port in the Windows Firewall.
To determine the ports in use, follow these instructions.
- On the computer with ExcelliPrint installed, open your Internet browser, and access the ExcelliPrint website (http://localhost:8080). Now choose View from the Log menu.
- Select Info. Choose High from the Network Detail drop list, None from Device Detail, and Low in Application Detail. Now click the View button.
- Scan the log for messages similar to PROTOCOL port xxxxx now accepting connections. You should have a single HTTP and one or more IPDS messages. You may also have an HTTPS message as well. Note each port number used in the Add Port Firewall Exceptions section.
Note: If you connect to ExcellePrint only from the local computer, it is not necessary to add exceptions for HTTP and HTTPS ports.
Now that you have determined which port numbers need to be allowed to add an exception to the Windows Firewall for each port. To add the firewall exceptions, follow these instructions.
- Open the Control Panel. In Category view. Next, click System and Security. Beneath Windows Defender Firewall, click Check Firewall Status.
- Determine the status of the Windows Firewall. If the Windows Firewall is off, then it is not blocking connections from your host system. It may still be a good idea to add the port exceptions if you turn the firewall on later.
- Click the "Allow another app..." button. In the "Add an App" dialog, enter a port number (i.e. ) on which to allow data in the Port Number field and provide a name for the exception. We suggest using a descriptive name such as the one shown in the graphic. In this case, is the protocol and is the program requiring the exception. Repeat this step to add an exception for each port is configured to use.
- If not found, click the "Allow another app..." button. In the "Add an App" dialog, click Browse and locate the executable you wish to allow. By default, the RPM program is RpmSrv.exe in C:\Program Files\Brooks Internet Software\RPM for RPM and C:\Program Files\Brooks Internet Software\ExcelliPrint\EPrintSrv.exe for ExcelliPrint. Click Add.
- Verify all exceptions are listed in the Programs and Services list and press the OK button to accept the changes and dismiss the dialog. Press OK on the network connection's "Properties" dialog to apply the changes.
Note: Do not make any changes to the existing exceptions.
Your new firewall exceptions will take effect immediately.
Brooks products use firewall exceptions
This topic first came up for us many years ago at the time Microsoft added a firewall to Windows XP. Naturally, we found as soon as the first user tried to run one of our products; consequently, this may be one of the longest-running pages on our website.
If you need a good software print server, please give our RPM Remote Print Manager product a try! Download the free 21-day trial and see what it can do for you. Be sure your firewall is open on ports 515 and 9100, and that you're not already running the Microsoft TCP/IP services module.