UDP port 123 is commonly associated with time synchronization services, but the practical question is not just whether the port number exists. On Windows, you usually need to confirm two different things: whether a local process is listening on UDP 123, and whether packets can travel across the network path to reach it. UDP is connectionless and does not provide TCP-style connection states, so the meaning of an “open” result is different from what many people expect [1].

What UDP port 123 means on Windows
A UDP port is identified by number, but the protocol itself does not establish a session the way TCP does [1]. That means a port can be configured for listening without any ongoing connection state to inspect. If you are troubleshooting a Windows machine you own or administer, start by identifying whether a local service is bound to UDP 123 before you test the network path.
Why UDP port checks differ from TCP checks
A TCP port checker cannot reliably confirm UDP port 123, because TCP and UDP are different protocols [2]. A TCP test may report success or failure for a TCP listener, but that does not prove anything about UDP. For UDP, a probe may also fail to produce a reply even when the packet arrived, so absence of a response is not the same thing as proof that the port is closed [6].
Check whether Windows is listening on UDP 123 locally
On the Windows system itself, use built-in tools to look for a local UDP endpoint. Microsoft documents netstat as a way to show activity on TCP and UDP ports, and netstat -a is recommended for that purpose [5]. If you want to narrow the output to UDP only, netstat -p udp limits the listing to UDP entries [3].
PowerShell also provides Get-NetUDPEndpoint, which returns current statistics and local or remote UDP port information for UDP endpoints [4]. This is useful when you want a scriptable view of the machine’s current UDP bindings. If UDP 123 appears in the local output, that tells you a process is listening on that port on that computer; it does not by itself prove that other hosts can reach it.
Test whether traffic can reach UDP 123 from another host
To check network reachability, you need a second host on the path, such as another Windows machine on the same network or a remote system you control. Microsoft’s PortQry can query UDP ports, but UDP results may depend on whether the target service responds to the probe [6]. That makes it useful for reachability testing, but not for proving an open UDP port in the same way a TCP handshake would.
In practice, the best confirmation is an application-level response. For example, if the service on UDP 123 is expected to answer a valid query, a reply shows that the packet reached the service and that the service processed it. If there is no reply, you still need to check the listener, local firewall, routing, and any upstream filtering before deciding the port is blocked.
How to interpret common results
If netstat or Get-NetUDPEndpoint shows UDP 123 on the local Windows system, that usually means a local listener exists [3][4]. If a remote UDP probe gets a response, that strongly suggests the path is working and the service is reachable [6]. If a remote probe gets no response, the result is inconclusive on its own because UDP does not guarantee a reply [1][6].
A useful mental model is this: local listing answers “is anything bound here?” while remote testing answers “can packets make it there and elicit a response?” Those are related questions, but not the same one. A port can be listening locally while still appearing unreachable from another host because a firewall, router rule, or upstream filter drops the traffic.
If UDP 123 looks blocked
If the local listener is missing, verify the Windows service or application that should own UDP 123 and confirm that it is actually running. If the listener exists but remote checks fail, review Windows Firewall rules on the host, then check any router or upstream filtering on the path you administer. Because you own or administer the systems involved, focus on devices and policies you can change rather than assuming the port is closed globally.
When troubleshooting, separate three layers: the service, the host firewall, and the network path. A service may be active but bound only locally; a firewall may allow the service internally but block external UDP; or the path may deliver the packet while the service chooses not to answer. Each of those cases needs a different fix.
When to use built-in Windows tools versus a remote checker
Use built-in Windows tools first when you need to verify a local listener or script repeatable checks on the machine itself. netstat, netstat -p udp, and Get-NetUDPEndpoint are the most direct options for local verification [3][4][5]. Use a second host or a tool like PortQry when you need to test whether UDP packets can actually reach the Windows system from elsewhere [6].
For UDP port 123, the most reliable workflow is local check first, then remote test, then interpretation. That sequence helps you avoid false conclusions from a no-response probe and keeps the troubleshooting focused on the network you control. If you only need to know whether a remote UDP probe answered, remember that the result is evidence of reachability, not a universal guarantee that the port behaves like a TCP open port [1][2][6].
Conclusion
Checking UDP port 123 on Windows is best treated as a verification problem, not a simple open-or-closed scan. Start with local listener tools on the Windows host, then confirm reachability from another host you control, and interpret no-response results cautiously. That approach separates local binding from network delivery and matches how UDP actually works [1][2][3][4][5][6].