> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-uk/p400/how-tos/how-to-establish-communications-between-the-ecr-and-the-p400+.md).

# How to Establish Communications Between the ECR and the P400+

How the P400+ connects to the ECR and to Verifone's gateway services once RNDIS configuration is complete.

## What is this?

Once the P400+ and the ECR have both been configured for RNDIS, the P400+ needs to be able to establish a connection to the ECR. This page explains what happens once that configuration is complete, assuming the pre-configured IP address on the P400+ is used.

{% hint style="info" %}
This page assumes you have already completed both Configuring the Payment Device to Support RNDIS and Configuring the ECR (MS Windows) for RNDIS. If connectivity isn't working as expected, see How to Check RNDIS Operation.
{% endhint %}

## How it works

By default, the P400+ uses the Ethernet adaptor in the ECR to access the internet and establish connectivity with Verifone's gateway services, for both transaction processing and estate management.

* The merchant is responsible for ensuring networking equipment and firewall settings are configured appropriately.
* The P400+ is always responsible for establishing outbound connections to Verifone's gateway service, for all interactions — the gateway does not initiate connections to the P400+.

## Related topics

* RNDIS Protocol Configuration
* How to Configure the P400 to support RNDIS
* How to Configure the ECR (MS Windows) for RNDIS
* How to Check RNDIS Operation


---

# 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.verifone.com/support-uk/p400/how-tos/how-to-establish-communications-between-the-ecr-and-the-p400+.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.
