Netmaker

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.

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

Make sure WireGuard is installed first: <a href="https://www.wireguard.com/install/" rel="nofollow noopener noreferrer" target="_blank">https://www.wireguard.com/install/</a> . It should not be necessary, but will allow you to troubleshoot, and also makes the speed faster, because you will be using Kernel WireGuard.

If you install WireGuard after Netclient, reinstall the netclient

After joining network, run "wg" to test if the interface is running and bytes are being transferred.

If after 1-2 minutes there are still no peers when you examine the output of "wg", try running "<b>netclient pull</b>". The peers should now show. It may take 1 minute before bytes are successfully transferring.

1. Make sure WireGuard is installed first: <a href="https://www.wireguard.com/install/" rel="nofollow noopener noreferrer" target="_blank">https://www.wireguard.com/install/</a> . It should not be necessary, but will allow you to troubleshoot, and also makes the speed faster, because you will be using Kernel WireGuard.
2. If you install WireGuard after Netclient, reinstall the netclient
3. After joining network, run "wg" to test if the interface is running and bytes are being transferred.
4. If after 1-2 minutes there are still no peers when you examine the output of "wg", try running "<b>netclient pull</b>". The peers should now show. It may take 1 minute before bytes are successfully transferring.

Issues With Netclient on Windows Server 2016

Find answers and get help from Intercom Support and Community Experts

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you