Kaseya Firewall Ports
Document Actions
Agent
From the perspective of a client computer which would probably be a server or desktop computer that is being monitored
| Source Port |
Destination | Destination IP | Protocol | Purpose |
|---|---|---|---|---|
| random | 5721 | KCS | TCP | Monitoring |
| 5721 | 5721 | KCS | UDP | Live Connect |
Server
| Source Port | Destination Port | Destination IP | Protocol | Purpose |
|---|---|---|---|---|
| random | 5721 | Kaseya HQ | TCP | Licencing & Updates |
| random | 25 | Mail Server | TCP | Server generated E-Mail |
| 80 | listen | n/a | TCP | Technican HTTP connections |
| 443 | listen | n/a | TCP | Technician HTTPS connections |
Technician
| Source Port | Destination Port | Destination IP | Protocol | Purpose |
|---|---|---|---|---|
| random | 80 | KCS | TCP | HTTP connection to Kaseya Server |
| random | 443 | KCS | TCP | HTTPS connection to Kaseya Server |
| 5721 | 5721 | Client | UDP | Kaseya Live Connect |
All the above TCP and UDP traffic is NAT capable. I've not investigated Kaseya's modified FTP over TCP 5721, but I don't believe it requires any special NAT/FTP helper for this.
See MS documentation re MS SQL server ports - probably TCP destination port 1433 and UDP source & destination port 1434, on both the Kaseya Server and the MS SQL Server only, does not apply to clients or remote technicians.
This info will allow you to operate properly with secure corporate networks, such as those found in government, health organisations or similar highly secure networks.
What is Kaseya
It is a Monitoring and Administration tool for a technical support company to support customer corporate networks, servers and workstations.
KCS implements Kaseya as part of its managed services and also utilises it as one of the methods to implement anti virus, anti malware and some aspects of disaster recovery.
Author:
Last modified Mar 01, 2012 02:01 PM
Previous:
Blog
