> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/references/references-classic/database-information-and-organization-classic/status-of-tcp-connections-classic.md).

# Status of TCP connections (classic)

The status of a TCP connection can be one of the following:

**established**\
The remote party has accepted the TCP connection and it is still active.

**closed**\
The system closed the TCP connection after it was successfully established.

**no service**\
The remote party acknowledged the initial SYN message by an RST message, for example the remote party does exist, but no service is bound to the request port. Most personal computers are protected by a firewall that discards RST messages to prevent effective port scanning.

**no host**\
The remote party does not acknowledge the SYN message, for example, the remote party does not exist or it is protected by a firewall.

**rejected**\
The operating system itself rejected the TCP connection, possibly due to security settings.


---

# 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://docs.nexthink.com/references/references-classic/database-information-and-organization-classic/status-of-tcp-connections-classic.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.