> 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/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-testing-the-connection-w.md).

# Test a Mobile Client connection without a mobile device

Test legacy Mobile Client network connectivity without using a mobile device.

**Only works on v8.00 and earlier.** Use the **MobileClientTlsTest Utility**, from the Gallagher File Transfer site → Command Centre and Associated Files → Utilities:

1. Download the file and its note.
2. Expand into a test directory and rename as instructed.
3. Create a test Mobile Client device in Command Centre and copy the generated Key.
4. Run the tool, paste the key.
5. Success dialog means the issue is **networking**.
6. Errors mean you should inspect the tool's log.
7. If unresolved, collect this tool's logs, Command Centre logs and a current FTSupport tool capture for a Senior or Developer.

***

🔗 **Related**

* [Unable to add a Mobile Client](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-unable-to-add-a-mobile-c.md). Ports and certificate binding.


---

# 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/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-testing-the-connection-w.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.