> 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/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-firewall-issues.md).

# Firewall issues

Diagnose and resolve firewall rules that prevent a Controller 7000 from connecting.

> 📋 **Prerequisites:** If the controller has never been online, work through [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md) first. Confirm the [Ports](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ports.md) the controller needs are open.

This guidance also applies to Controller 7000 SDC.

{% hint style="warning" %}
If Windows Firewall has not been correctly configured, it may block connections to controllers and cause them to stay offline.
{% endhint %}

***

#### How do I know the firewall is what's blocking my controllers?

**Quick test:** Temporarily disable the Windows Firewall. If the controllers come online, the firewall is the issue.

***

## Configuration at installation time

#### Which firewall rules does Command Centre need?

When Command Centre is installed, Windows Firewall rules are automatically added.

> **Important:** If controllers or workstations will be on **different subnets** to the server PC, un-tick **"Allow communication on local subnet only"** during Command Centre installation.

***

## Adding firewall rules after installation

#### How do I add or update those rules after installation?

1. Open Windows Firewall: Start > Control Panel > search "firewall" > click Windows Firewall.
2. In the left pane, click **Advanced settings**. (Provide admin password if prompted.)
3. In the Windows Firewall with Advanced Security dialog, in the left pane, click **Inbound Rules**.
4. In the right pane, click **New Rule**.
5. Follow the **New Inbound Rule** wizard.
6. Add the following programs:
   * `CCNTBertServ.exe` (FT Controller Service)
   * `CCNTSad.exe` (FT Command Centre Service)

***

## Updating existing firewall rules

1. From the **Inbound Rules** panel, click the rule to modify. For example, **FT Controller Service**, which is the service that communicates with controllers.
2. Open the **Scope** tab of the Inbound Rules Properties.
3. If connections were restricted to the local subnet during installation, either:
   * Add additional IP scopes, or
   * Select **Any IP address**.

***

🔗 **Related**

* [Ports](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ports.md). The ports the firewall rules need to allow.
* [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md). Full connection setup and testing, including netstat checks for a locked port 1072.
* [Controller 7000](broken://pages/873trKCrdhjXzfqYdsdU). Variants, specifications, and accessories.


---

# 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/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-firewall-issues.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.