> 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/configure/controller-7000-use-cases-for-use-diff.md).

# Use Cases for Use Different IP Addresses for Server

Use different server IP addresses for Controller 7000 and Controller 7000 SDC network and disaster-recovery scenarios.

#### What does the "Use different IP for Server" field do?

The **"Use different IP for Server"** field in Command Centre (Controller Properties > Setup tab) overrides the default resolved IP address that CC sends to controllers as the server IP.

This configuration also applies to Controller 7000 SDC.

By default, CC resolves the server IP by pinging the PC's hostname, and the returned IP is what gets sent to the controller. The "Use different IP for Server" field bypasses this automatic resolution.

***

#### When to use the "Use different IP for Server" field

There are three primary scenarios where this field is required:

1. **Controller connecting to the server via the internet**
   * The controller only has visibility of the gateway IP (the internet-facing address), not the server's internal IP.
   * The gateway IP is entered in the "Use different IP for Server" field.
   * Route commands on the gateway/router are used to forward traffic to the Command Centre server.
2. **Server has multiple network adapters and controllers are on different adapters**
   * The adapter binding order cannot be changed, or controllers connect to two different adapters.
   * Use "Use different IP for Server" to specify the IP address of the secondary adapter that controllers on that segment should use to reach the server.
3. **Migrating a controller to a new server**
   * During a server migration, use "Use different IP for Server" to point the controller to the new server's IP address without waiting for the automatic binding order resolution to update.

***

#### How does the controller use the IP I enter?

Specifying "Use different IP for Server" causes CC to send that IP address to the controller as the server IP, instead of the automatically resolved IP from the adapter binding order.

The controller then uses this IP when making its outbound TCP connection to the server on port 1072.

> **Installer note:** Always verify the IP you enter in "Use different IP for Server" is reachable from the controller's network segment. After applying, do a Push Configuration and check the controller's TCP Sender web page to confirm it has received the correct server IP.

***

🔗 **Related**

* [Dynamic DNS](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-dynamic-dns.md). Another way to redirect controllers to a different server, used for disaster recovery.
* [Testing Controller Connections](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-testing-controller-con.md). Confirm the new server IP with the TCP Sender web page.
* [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md). Where the Setup tab and Push Configuration fit in.


---

# 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/configure/controller-7000-use-cases-for-use-diff.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.