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 ...
Block network ports
You can block access to network ports with BrowseControl. BrowseControl has the ability to control network protocol ports with its Port Filter. Administrators can easily enable or disable network ports on the network by adding the ports to the Port ...
I have terminal servers and workstations. Do I need two licenses for each user?
CurrentWare’s licensing model is based on either the number of machines or users depending on your organization’s network infrastructure. If your network infrastructure consists of both terminal servers and workstations you will require user-based ...
I upgraded my CurrentWare to the latest version, do I need a new license key?
The transition from an older version of CurrentWare to a newer one is smooth as the key remains valid and there’s no need for users to re-register. It’s important to note that subscription keys are specific to each version at the time you register ...
System Requirements
CurrentWare is designed to work seamlessly with a wide range of computers running Windows operating systems, including both 32-bit and 64-bit platforms. The Web Console offers exceptional versatility, as it can be accessed from any browser and any ...