# IRPCTest.TestConnectionToRemoteServer

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Vault API](https://developer.m-files.com/APIs/gRPC-API/vault/index.md) > [Connection and health checks](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCTest/index.md)

HTML version: https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCTest/TestConnectionToRemoteServer/

Badges: `Vault API / standard` `write` `no session`

Asks this server to connect to another M-Files Server and call `TestConnectionToServer` there.
Normally disabled.

- **Service:** [Connection and health checks](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCTest/index.md) `MFiles.IRPCTest`
- **gRPC method:** `/MFiles.IRPCTest/TestConnectionToRemoteServer`
- **HTTP (mf-http-grpc):** `POST /grpc/v1/test-connection-to-remote-server`
- **Request:** [`TestConnectionToRemoteServerRequest`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCTest/TestConnectionToRemoteServer/index.md#request)
- **Response:** [`TestConnectionToRemoteServerResponse`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCTest/TestConnectionToRemoteServer/index.md#response)
- **Book and level:** Vault API, standard
- **Kind:** write
- **Session:** Not needed: the call can be made before logging in.
- **Idempotent:** no
- **Returns metadata structure version:** no
- **Streaming:** none (unary)

<a id="remarks"></a>

## Remarks

Needs no session. Unless the server enables cached replica connections, which is normally
disabled, the call fails with `E_MFILES_CONFIGURING_REPLICA_VAULTS_NOT_ALLOWED` ("M-Files no
longer supports the creation of replica vaults."). That check comes first, so the server makes no
connection in that case. Applications have no use for this method; to test your own connection to
a server, call [TestConnectionToServer](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCTest/TestConnectionToServer/index.md) on that
server.

<a id="request"></a>

## Request: TestConnectionToRemoteServerRequest

> Nested message fields are expanded to depth 3; follow a type link for deeper levels and for the type's own page.

| Field | Type | Description |
|---|---|---|
| `remote` | [`ServerAddress`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.ServerAddress/index.md) | The MS-RPC address of the other server. Used only where the feature is enabled. |
| `remote.network_address` | `string` | The network address (name) of the server. |
| `remote.endpoint` | `string` | The endpoint of the server. |
| `remote.protocol_sequence` | `string` | The protocol sequence of the server. |

<a id="response"></a>

## Response: TestConnectionToRemoteServerResponse

No fields.

<a id="related"></a>

## Related methods

- [TestConnectionToServer](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCTest/TestConnectionToServer/index.md): Does nothing and returns at once. Use it to check that calls reach the server and to measure the round-trip time.