[GH-ISSUE #5488] Netbird issue when running on Windows server with DNS role installed #11563

Open
opened 2026-08-05 01:30:03 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @Geertkok1 on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5488

Describe the problem

Netbird runs into a problem with UDP port 51820 being is use when it is running on a Windows server running DNS server role

To Reproduce

Steps to reproduce the behavior:

  1. Install DNS role on Windows server
  2. Install Netbird
  3. Try to connect Netbird
  4. See error Error: daemon up failed: call service up method: rpc error: code = DeadlineExceeded desc = context deadline exceeded on screen(in cmd)

Expected behavior

Netbird connecting without issue

Are you using NetBird Cloud?

We are using Netbird Cloud

NetBird version

0.66.0

Is any other VPN software installed?

No

Debug output

client/internal/engine.go:503: failed to pull up wgInterface [wt0]: listen udp4 :51820: bind: Each socketaddres s(protocol/netwerkaddress/port) can only be used once.

Screenshots

Additional context

Add any other context about the problem here.

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings

How we work around the issue
We have done the following steps to find the cause of the issue and created a work around:

  1. Check using netstat -aon what process was using port 51820
  2. Found out that the dns server process was using it(and ports around 51820
  3. Found out using google that this was expected behaviour
  4. Use dnscmd /Config /SocketPoolExcludedPortRanges <FirstPort>-<LastPort> to exclude ports used by netbird client
  5. See that the netbird client connect without issue

This is a quick workaround for the issue but official fix would probably be better. Or at least a reference in the documentation for other users to keep in mind.

Originally created by @Geertkok1 on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5488 **Describe the problem** Netbird runs into a problem with UDP port 51820 being is use when it is running on a Windows server running DNS server role **To Reproduce** Steps to reproduce the behavior: 1. Install DNS role on Windows server 2. Install Netbird 3. Try to connect Netbird 4. See error Error: daemon up failed: call service up method: rpc error: code = DeadlineExceeded desc = context deadline exceeded on screen(in cmd) **Expected behavior** Netbird connecting without issue **Are you using NetBird Cloud?** We are using Netbird Cloud **NetBird version** 0.66.0 **Is any other VPN software installed?** No **Debug output** client/internal/engine.go:503: failed to pull up wgInterface [wt0]: listen udp4 :51820: bind: Each socketaddres s(protocol/netwerkaddress/port) can only be used once. **Screenshots** **Additional context** Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings **How we work around the issue** We have done the following steps to find the cause of the issue and created a work around: 1. Check using netstat -aon what process was using port 51820 2. Found out that the dns server process was using it(and ports around 51820 3. Found out using google that this was expected behaviour 4. Use `dnscmd /Config /SocketPoolExcludedPortRanges <FirstPort>-<LastPort>` to exclude ports used by netbird client 5. See that the netbird client connect without issue This is a quick workaround for the issue but official fix would probably be better. Or at least a reference in the documentation for other users to keep in mind.
saavagebueno added the triage-needed label 2026-08-05 01:30:03 -04:00
Author
Owner

@sandroshu commented on GitHub (Mar 3, 2026):

51820 is the default port for Wireguard.
Windows dns server seems like randomly taking ports. Exclude the 51820 and restart your PC or DNS service.
dnscmd /Config /SocketPoolExcludedPortRanges 51820

<!-- gh-comment-id:3990881569 --> @sandroshu commented on GitHub (Mar 3, 2026): 51820 is the default port for Wireguard. Windows dns server seems like randomly taking ports. Exclude the 51820 and restart your PC or DNS service. `dnscmd /Config /SocketPoolExcludedPortRanges 51820`
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11563