> 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-6000/configure/controller-6000-use-cases-different-ip-for-server.md).

# Use Cases for Using Different IP Addresses for Server

Configure a Controller 6000 to use a different Command Centre server IP address.

There are some scenarios where the controller **must use a different IP Address for the Server** than the one Command Centre auto-resolves from the host name.

## Three primary use cases

1. **Controller connecting to the server via the internet.** The controller requires the **Gateway IP Address** (this is the only address exposed to the internet). Route commands are then used to forward the data to the Command Centre server.
2. **Adapter Binding Order cannot be changed** (for example, on Windows 10 and above where binding order has been removed) **or controllers are on 2 different adapters**, and you need to specify an IP Address for a secondary adapter.
3. **Migrating a controller to a new server.** Using this option allows the controller to connect to the new server during the migration window.

***

## How it works

By specifying the **Use different IP for Server** field on the Controller Properties > Setup tab, you are **overriding** the default resolved IP Address that is sent to the controllers to use as the Server IP Address.

For server-side multi-NIC binding order (Windows 7 / Server 2012 and older), see [Command Centre Server has Multiple Network Adaptors](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-command-centre-server.md).

For Wireless adapter binding behaviour, see [Wireless Adaptor on the Server](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-wireless-adaptor-on-server.md).

***

🔗 **Related**

* [Command Centre Server has Multiple Network Adaptors](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-command-centre-server.md). Server-side binding order.
* [Wireless Adaptor on the Server](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-wireless-adaptor-on-server.md). The wireless-adapter case.
* [Assigning a Controller an IP address](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-assigning-a-controller.md). Where the field is set.


---

# 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-6000/configure/controller-6000-use-cases-different-ip-for-server.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.
