> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/network-ports-and-protocols/ports-by-component.md).

# Ports by component

Ports, directions, and version-specific firewall requirements.

## Ports by component

### Controllers to Command Centre Server

**v6.0 and higher:**

| Keyword   | Port         | Purpose                                          |
| --------- | ------------ | ------------------------------------------------ |
| bootps    | 67/udp       | BootP server (IP assignment, if used)            |
| bootpc    | 68/udp       | BootP client                                     |
| HTTP      | 80/tcp       | IE to FTController connection (web browse)       |
| Gallagher | **1072/tcp** | FTController connection. Enable bi-directionally |

> **Version behaviour:** **v8.50+** only needs **1072/tcp inbound** from controllers. This applies once every controller uses the current server version. When any controller runs **v8.40 or below**, the server also needs outbound access.

**v5.21 and lower:**&#x20;

Additionally `ftp 20 & 21/tcp` for software download through CCFT Server. TCP 1072 is always required. If a controller has a gateway, enable **ICMP** between the controller and gateway.

### Clients and other components to Server

| Path                                 | Port(s)                                                                                 |
| ------------------------------------ | --------------------------------------------------------------------------------------- |
| Config Client (v7.90+)               | 8905/tcp (configurable)                                                                 |
| Config Client (v7.80 and lower)      | 135/tcp (epmap) + DCOM 5× dynamic + 1072/udp (Intercom)                                 |
| Command Centre Client                | 445/tcp (ClickOnce) + 4840/tcp (configurable)                                           |
| Mobile Client                        | 8901/tcp (data) + 8902/tcp (enrolment)                                                  |
| Gallagher Cloud (Mobile Connect)     | 443/tcp HTTPS **outbound**; DNS `commandcentre-ap-southeast-2.security.gallagher.cloud` |
| Multi-Server                         | 4840/tcp OPCUA (configurable)                                                           |
| Visitor Management Client            | 445/tcp + 4243/tcp (configurable)                                                       |
| Visitor Management Kiosk             | 445/tcp + 4840/tcp (configurable)                                                       |
| Sagem/Morpho/IDEMIA biometric reader | 11010/tcp (CC to reader) + 11011/tcp (secure)                                           |

### Salto to Server

| Port                | Protocol | Direction    | Purpose                                            |
| ------------------- | -------- | ------------ | -------------------------------------------------- |
| 1100                | UDP      | Server to CU | Handshake                                          |
| 5000–10000          | UDP      | CU to Server | Online controllers to server (one port per client) |
| 5000–10000          | TCP      | Bi-dir       | Encoders                                           |
| 8099                | TCP      | Bi-dir       | Service to software (or another 8000-range port)   |
| 1433 TCP / 1434 UDP | —        | Bi-dir       | Editing and Database                               |
| 8100 / 8101         | TCP      | Bi-dir       | SALTO Web authentication / reporting               |

> Do not block `SaltoServiceConfigurator.exe`, `RWProAccessForService.exe`, or `HAMSForService_SQL.exe`.&#x20;
>
> CU means Control Unit, such as an update point or door controller.

### Controller 6000 specific

| Port               | Protocol | Direction | Purpose                                                 |
| ------------------ | -------- | --------- | ------------------------------------------------------- |
| 80\*               | TCP      | In        | Tech Support Diagnostics (HTTP)                         |
| 137† / 138†        | UDP      | In        | NetBIOS-over-TCP/IP browsing                            |
| 1072               | TCP      | In        | Comms with server and other C6000s (encrypted Bertbus)  |
| TCP-stack assigned | TCP      | Out       | IP Alarms (DC09, if configured); server and C6000 comms |

\* Port 80 opens when **DIP Switch 1 is ON**. † Ports 137 and 138 open when **DIP Switch 6 is OFF**.

* Port 135 initiates the Client/Server connection. Port 1072 is only needed for the CC Client if **intercom** is required.
* CC Camera live viewing uses a dynamically assigned camera-to-client UDP port. You cannot restrict this port.
* Premier Client uses TCP 445 only with ClickOnce, not copied client files.

### Related

* [Controller Listen Ports](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-software/configure/server-configuration/README.md)
* [Controller 7000 - Ports](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ports.md)
* [Controller 6000 - Ports](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-hardware/controllers/controller-6000/reference/controller-6000-ports.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/network-ports-and-protocols/ports-by-component.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
