> 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-check-rndis-operation.md).

# How to Check RNDIS Operation

Confirm that an RNDIS (IP-over-USB) connection between the ECR and the P400+ is working.

{% hint style="info" %}
**Use this when** you have configured RNDIS on both the P400+ and the ECR, and you need to confirm the connection is working.
{% endhint %}

{% hint style="warning" %}
**Do NOT use this when** you haven't yet configured both sides of the connection (see How to Configure the P400 to support RNDIS and How to Configure the ECR (MS Windows) for RNDIS).
{% endhint %}

This page explains how to check that an RNDIS connection between the ECR and the P400+ is working. This is the third and final stage in setting up RNDIS — see RNDIS Protocol Configuration for the full picture.

{% hint style="info" %}
**Before you start.** You will need the Supervisor password to run a ping from the P400+.
{% endhint %}

## Check the connection

{% stepper %}
{% step %}

### Ping the P400+ from the ECR

Use the `ping` command from the control panel on the ECR to confirm connectivity to the P400+, using the static IP address configured on the P400+ (typically `192.168.137.2`).
{% endstep %}

{% step %}

### Ping the ECR from the P400+

Log in to the communications management system on the P400+, and use the ping command to prove connectivity to the ECR (the ECR IP is typically `192.168.137.3`). Navigate the menu as directed — you will need the Supervisor password to access this facility.
{% endstep %}

{% step %}

### Check the result

Check that a response was received on the results screen. Use the back button to return to the ping screen.
{% endstep %}

{% step %}

### Check internet access

Check that the P400+ can access the internet. Use the ping command on the P400+ as above, but with a common public IP address such as `001.001.001.001`.
{% endstep %}
{% endstepper %}

## Guidelines

* The P400+'s static IP in an RNDIS setup is typically `192.168.137.2`; the ECR's is typically `192.168.137.3`.
* If any connectivity check fails, check your configuration first. Some versions of Windows have an issue with the Internet Connection Sharing service not starting — see [Microsoft's guidance](https://support.microsoft.com/en-gb/help/4055559/ics-doesn-t-work-after-computer-or-service-restart-on-windows-10).
* After applying Microsoft's fix, set the connection sharing configuration back to "not sharing" and then reapply sharing — ICS should then work on the ECR.
* Firewall settings should also be checked, to enable ICS and allow outbound calls from the P400+ across the shared connection.

## FAQ

<details>

<summary>What IP addresses should I expect to ping?</summary>

Typically `192.168.137.2` for the P400+ and `192.168.137.3` for the ECR.

</details>

<details>

<summary>The ping fails — what should I check first?</summary>

Check your RNDIS configuration on both the P400+ and the ECR, then check Internet Connection Sharing and firewall settings on the ECR.

</details>

<details>

<summary>How do I check the P400+ has internet access?</summary>

Run a ping from the P400+ to a common public IP address such as `001.001.001.001`.

</details>

<details>

<summary>Keywords</summary>

Also called: RNDIS connectivity check, ping test, RNDIS troubleshooting. Search terms: ping, RNDIS, Internet Connection Sharing, ICS, P400+.

</details>


---

# 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-check-rndis-operation.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.
