> 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-testing-controller-con.md). # Test controller connections Test Controller 7000 network connectivity, port 1072, server communication, and diagnostics. > 📋 **Prerequisites:** Know the controller and server IP addresses. If the controller has never come 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. A toolkit for diagnosing network connectivity issues between a C7000 controller and the Command Centre server. This procedure also applies to Controller 7000 SDC. > **Best practice:** The majority of these tests are best run from the controller's network connection point using a laptop, back to the server. Ideally, configure the laptop with the same IP settings as the controller and plug it into the same network connection point. From version 9.30 onwards, the controller can perform these tests itself (see Network Connectivity Tools below). *** ## Ping #### How do I confirm a controller can reach the server on the network? ``` C:\>ping C:\>ping ``` A reply confirms a network connection exists. It also populates the ARP cache (required before running ARP). **Ping may fail if:** * No route exists to the controller * ICMP protocol is disabled on the site network If ping is disabled, the test may fail even when a valid network connection exists. **Check the Link Light:** the green LED next to the Ethernet port on the controller should be solid on. > **Note:** If ping returns an IPv6 address, force IPv4 with: `ping -4 ` > **Cross-subnet:** If the controller is on a different subnet to the server, the switch the controller is plugged into must reply to pings. The controller pings the gateway to confirm connectivity before transmitting data to the server. *** ## Listen port #### Which tools test port 1072? Default communication port: **Port 1072** (defined as the Listen Port in the Gallagher Registry). Unless a unique Listen Port has been configured, port 1072 is always used after installing Command Centre. > **Note:** If the site uses a non-standard listen port, the controller must first connect to the server to pick up that port. *** ## Telnet ``` C:\>telnet 1072 ``` Tests TCP port 1072 (controller-to-server and controller-to-controller communication). > **Important:** Run the telnet test in both directions: controller to server **and** server to controller. > **Note:** If you get "'telnet' is not recognized", install from Control Panel > Programs and Features > Turn Windows features on or off. Install both **Telnet Client** and **Telnet Server**. **Interpretation:** | Result | Meaning | | -------------------------------------- | ---------------------------------------------------------------------------------------- | | Screen blanks, cursor flashes top-left | Port is **OPEN** (OK) | | Cursor returns to C: prompt | Port is **OPEN** (OK) — may see connection-lost message or alarm if controller is online | | Connection refused / error message | Port is **BLOCKED** (FAIL) | **If blocked, check:** 1. Windows Firewall or third-party firewall. See [Firewall Issues](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-firewall-issues.md). 2. Ask IT if the port is blocked at Switch/Router level. 3. Anti-virus. Some corporate AV software prevents controller connections; temporarily disable to test. *** ## Telnet alternative: PowerShell TNC (preferred) ```powershell PS C:\Users\Gallagher> tnc [ip address] -p [port number] ``` Example: `tnc 10.20.82.199 -p 1072` ![TNC command result](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d41b4dd7cf77c363efbde40a14aba9c233919d75%2FSECHUB-C7000-TESTING-01-tnc-command-result.png?alt=media) **Advantages over Telnet:** 1. No Telnet client installation required 2. Shows which Server IP and Network Adapter are used to communicate with the controller *** ## Network Connectivity Tools (v9.30+) Available from CC version 9.30 onwards, directly from the controller's web pages (both the Web Config and Debug pages). **Access:** Click the **Network Connectivity Tools** link in the controller's web interface. ![Network Connectivity Tools entry](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d5f6fb7ffbc95c0f3a7752fdce0744b26936419b%2FSECHUB-C7000-NETWORKING-01-network-connectivity-tools.png?alt=media) The dialog: ![Network Connectivity Tools dialog](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-9aed1370c132751710210543702e224e4cf5efc8%2FSECHUB-C7000-NETWORKING-02-network-connectivity-tools-dialog.png?alt=media) By default, the dialog pre-fills the Gallagher Controller Service listen port (1072). Enter the server's IP address and click **ConnectToIPAddress**. Successful connection to port 1072: ![Successful connection](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-cf815f09783cd1bc4ed5a831323a3c86c0c04e7e%2FSECHUB-C7000-NETWORKING-04-network-connectivity-success.png?alt=media) Failed connection (port not responding): ![Failed connection](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-07182e40fa8ead28200731005fb1f7bc8c3726be%2FSECHUB-C7000-NETWORKING-05-network-connectivity-fail.png?alt=media) The tool is also accessible from the Debug main page: ![Network Connectivity Tools from debug page](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-13a87fdc9101fc5488038041f774f441b59919ab%2FSECHUB-C6000-TESTING-05-network-connectivity-tools-debug.png?alt=media) *** ## ARP ``` C:\>arp -a ``` Run after pinging the controller. Confirms you are receiving a reply from an actual Gallagher controller. Find the Internet Address you pinged. **If the Physical Address starts with `00-90-1d` it is a Gallagher controller.** *** ## Netstat #### How do I confirm another application is not holding port 1072? ``` C:\>netstat -an C:\>netstat -ano ``` ### CC version 9.00 and above: one connection ![Netstat v8.50+ result](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e3334d104c03516ab0d397348abc8949017716de%2FSECHUB-C6000-TESTING-08.png?alt=media) From CC v8.50, there is only **ONE** connection established (controller to server). This is expected and correct behavior. ### Checking the server is listening on port 1072 ![TCP netstat port 1072 listening](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-de7fd967c4643b2da91425d3a52855ce5b950fb3%2FSECHUB-C6000-TESTING-03-netstat-ano-port-1072.png?alt=media) Run `netstat -ano`. The server should show LISTENING on port 1072, with a PID. Confirm that PID belongs to the FT Controller Service in Windows Task Manager. ![Task Manager PID list](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-431d2b79fd195822a57281b04a0444b4f3aa2b0d%2FSECHUB-C6000-TESTING-04-task-manager-pid.png?alt=media) > **Important:** If the PID of 'FT Controller Service' does **NOT** match the PID using port 1072, another application is locking port 1072 and causing the controller to fail to come online. ![Port conflict — wrong PID](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fb969a9af508e273f4591dbf8f26749d763f026c%2FSECHUB-C7000-TESTING-05-tcp-netstat-port-conflict.png?alt=media) **Solutions if another application has port 1072:** * **Option 1:** Get the third-party application to change or stop using port 1072. * **Option 2:** Change the listen port of the server-controller communication to a custom port (see the Listen Ports for Controllers documentation). *** ## Web browsing the controller Directly browse the controller's web interface to confirm IP configuration, verify certificates and keys, check the error log, and confirm the node number. **URL format:** `{controller-ip}/debug.` (trailing full stop is required) Example: `172.16.243.56/debug.` **Credentials:** | Condition | Logon | Password | | --------------------------- | ------------ | ------------------------------------------------------------------------------------- | | Controller in 2-flash state | `diagnostic` | `[REDACTED]` (default - contact Tech Support) | | Controller in 1-flash state | `diagnostic` | `[REDACTED]` (site-specific value based on Site Serial number - contact Tech Support) | | CC v8.40+ | `diagnostic` | May be a configured password - check with Tech Support | **Key diagnostic pages:** **TCPSender.** Primary page for confirming TCP/IP settings. Check the **"Server IP"** field. If it does not match the actual server IP, the controller will not come online. Active sessions show if the server is connected. **TCPExchange.** Confirms keys and certificates are valid and the correct Master certificate is selected (must match the Certificate setting on the Controller's Setup tab in CC). Active sessions show if the controller is connected to the server. **Errorlog.** Check as a last resort for recurring errors or restarts. **Node Number.** Verify the node number on the web page matches the node number in Command Centre. **To find the Node Number in CC:** 1. Open Controller Properties and select the **Setup** tab. 2. Hold **Ctrl** and double-click with the left mouse button in a clear area of the Setup tab. 3. A popup displays the controller's node number. ![Node number popup in CC](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-cb27ae4dc9075405ff3e9d48cda59b9fce7d6037%2FSECHUB-C7000-TESTING-07-node-number-popup.png?alt=media) *** 🔗 **Related** * [Ports](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ports.md). What each port is for, including port 1072. * [Firewall Issues](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-firewall-issues.md). What to change when telnet or TNC shows the port blocked. * [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md). The full first-connection workflow. --- # 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-testing-controller-con.md?ask=&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.