# Issues With Netclient on Windows Server 2016

## Issues With Netclient on Windows Server 2016

### Description

Some users have reported issues connecting to Windows Server 2016 after installing the netclient (v0.23.0). Unable to ping via Remote Access Client / Gateway.

### Recreation

Install Netclient on Windows Server 2016 via MSI, join network via enrollment key.

### Remediation Steps

{% stepper %}
{% step %}

### Install WireGuard

Make sure WireGuard is installed first: <https://www.wireguard.com/install/> . It should not be necessary, but will allow you to troubleshoot, and also makes the speed faster, because you will be using Kernel WireGuard.
{% endstep %}

{% step %}

### Reinstall Netclient (if applicable)

If you install WireGuard after Netclient, reinstall the netclient.
{% endstep %}

{% step %}

### Verify interface with wg

After joining network, run `wg` to test if the interface is running and bytes are being transferred.
{% endstep %}

{% step %}

### Pull configuration if no peers

If after 1–2 minutes there are still no peers when you examine the output of `wg`, try running `netclient pull`. The peers should now show. It may take 1 minute before bytes are successfully transferring.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.netmaker.io/help-articles/issues-with-netclient-on-windows-server-2016.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.