What ports need to be opened on my Firewall?
During the installation, CurrentWare will add the CurrentWare ports to your Windows Firewall exception list.
If you are having issues with console connections, client connections, or data upload, please make sure the following ports are not blocked on your CurrentWare Server computer.
Based on your solution(s) installed you may have different port requirements. See the proper table below for your port needed.
CurrentWare Suite
Ports and Protocol | What the ports handles |
8989-8992, 8995-8999 TCP/UDP | Client+Console connection and data upload ports |
8988 TCP/UDP | Live Capture feature – OPTIONAL – For BrowseReporter live capture feature |
8993 TCP/UDP | Screenshots Upload – For BrowseReporter screen capture |
8994 TCP/UDP | HTTPS Filtering – For BrowseControl blocking features |
1433-1434 TCP/UDP | For SQL Database only – OPTIONAL – If you find the 899x range ports are not providing dataflow
|
AccessPatrol
Ports and Protocol | What the ports handles |
8989-8992, 8995-8999 TCP/UDP | Client+Console connection and upload Ports |
1433-1434 TCP/UDP | For SQL Database only – OPTIONAL – If you find the 899x range ports are not providing dataflow
|
BrowseReporter
Ports and Protocol | What the ports handles |
8989-8992, 8995-8999 TCP/UDP | Client+Console connection and upload Ports |
8988 TCP/UDP | Live Capture feature – OPTIONAL – For BrowseReporter live capture feature |
8993 TCP/UDP | Screenshots Upload –OPTIONAL– For BrowseReporter screen capture |
1433-1434 TCP/UDP | For SQL Database only – OPTIONAL – If you find the 899x range ports are not providing dataflow
|
BrowseControl
Ports and Protocol | What the ports handles |
8989-8992, 8995-8999 TCP/UDP | Client+Console connection and upload Ports |
8994 TCP/UDP | HTTPS Filtering – For BrowseControl blocking features |
1433-1434 TCP/UDP | For SQL Database only – OPTIONAL – If you find the 899x range ports are not providing dataflow
|
enPowerManager
Ports and Protocol | What the ports handles |
8989-8992, 8995-8999 TCP/UDP | Client+Console connection and upload Ports |
1433-1434 TCP/UDP | For SQL Database only – OPTIONAL – If you find the 899x range ports are not providing dataflow |
Related Articles
Configure Firewall Rule for Remote Client Install
The client computer’s Windows Firewall may be blocking the setup file from being sent. Below are some recommendations for configuring the Firewall to permit the remote installation of the CurrentWare client. Option #1: Turn OFF Windows Firewall ...
Troubleshooting SQL Server Connection Issues with CurrentWare Server
If the CurrentWare Server is unable to connect to the SQL server, you may need to configure the Windows Firewall and SQL Server Configuration Manager to allow SQL Server access. Add the sqlsvr.exe into Window’s Firewall Inbound Rule list Go to ...
Adding CurrentWare to your BitDefenders Exclusion Lists
Bitdefender Antivirus can sometimes interrupt with the functionalities of CurrentWare due to where the local files are hidden on the client PCs. RECOMMENDED: Temporarily Disable Bitdefender Prior to Upgrades If you have any of the Bitdefender ...
Configure Port Forwarding for Remote Workers (SQL)
Connecting the CurrentWare Clients (Remote workers) To connect your CurrentWare Clients to the CurrentWare Server over the Internet, you will need to port forward the CurrentWare traffic from your network’s router to the CurrentWare Server computer. ...
How do I Setup CurrentWare with SQL Express
Welcome to the SQL Express Database Installation and Setup page. Benefits of using a SQL Database with the cwServer are an increase in overall performance and stability of client connections. Here are the steps to download, setup and configure your ...