> 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-configure-the-p400-to-support-rndis.md).

# How to Configure the P400 to support RNDIS

Set up the P400+ terminal to support RNDIS (IP-over-USB) connectivity to the ECR.

{% hint style="info" %}
**Use this when** you need to set up the P400+ terminal side of an RNDIS (IP over USB) connection to the ECR.
{% endhint %}

{% hint style="warning" %}
**Do NOT use this when** you only need a standard LAN/Ethernet connection (see How to Configure Ethernet on the P400), or when you are configuring the ECR side of the RNDIS connection — that is a separate stage (see Configuring the ECR (MS Windows) for RNDIS).
{% endhint %}

This page explains how to configure the P400+ payment device to support RNDIS. This is the first of three stages in setting up RNDIS — see RNDIS Protocol Configuration for the full picture.

{% hint style="info" %}
**Before you start.** You will need the Supervisor password.
{% endhint %}

## Configure the device for RNDIS

{% stepper %}
{% step %}

### Access the Supervisor menu

Turn on the P400+ by plugging it in to a power source. Press the `*` key on the keypad, or touch the blue Verifone logo banner. Select **Supervisor** and enter the Supervisor password.
{% endstep %}

{% step %}

### Enable RNDIS and reboot

From the Supervisor menu, enable RNDIS support. Once this setting has been made, the P400+ needs to be rebooted for the setting to take effect.
{% endstep %}

{% step %}

### Set the default communications protocol

The P400+ also needs to be configured to select the correct default communications protocol on start-up. Navigate to the Terminal Systems Menu and set the following:

| Setting       | Value                    |
| ------------- | ------------------------ |
| Mode          | Static                   |
| Speed         | Auto                     |
| AutoStart     | On                       |
| IP address    | 192.168.137.2            |
| Broadcast     | Leave blank              |
| Mask          | 255.255.255.0            |
| Gateway       | 192.168.137.1            |
| DNS 1         | 8.8.8.8                  |
| DNS 2         | 8.8.4.4                  |
| Interface     | Pre-set — miniusb        |
| MAC Address   | Pre-set — variable value |
| MTU           | Pre-set — default        |
| {% endstep %} |                          |

{% step %}

### Save and reboot

Exit the settings, making sure to save the configuration, then reboot the device.
{% endstep %}
{% endstepper %}

## Guidelines

* The static IP address for the P400+ in an RNDIS setup is typically `192.168.137.2`.
* Settings marked "pre-set" should not normally need to be changed.
* A reboot is required both after enabling RNDIS and after setting the communications protocol — don't skip either reboot.

## FAQ

<details>

<summary>What IP address does the P400+ use for RNDIS?</summary>

Typically `192.168.137.2`, with gateway `192.168.137.1`.

</details>

<details>

<summary>Do I need to reboot the terminal?</summary>

Yes — once after enabling RNDIS, and again after setting the communications protocol values.

</details>

<details>

<summary>What's next after configuring the payment device?</summary>

Configure the ECR (MS Windows) side of the connection, then check that the connection is working. See RNDIS Protocol Configuration for the full sequence.

</details>

<details>

<summary>Keywords</summary>

Also called: RNDIS setup, IP over USB, payment device RNDIS configuration. Search terms: RNDIS, static IP, Supervisor menu, Terminal Systems Menu, 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-configure-the-p400-to-support-rndis.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.
