WinDiscovery cannot discover the device

Symptoms

Causes

Incorrect client or server configuration
If the issue started suddenly, check for recent firewall, VLAN, or DHCP changes that could affect routing or service reachability
Network reachability or routing differences
Traffic blocked by firewall rules

Suggested solutions or troubleshooting steps

Verify the device is reachable from the client network.
Confirm clients can reach the device using the same path they use for time synchronization, not only from the local subnet.
Confirm required ports are allowed.
Ensure timing traffic is permitted by firewall and security rules. NTP uses UDP port 123.
If it worked previously, review recent network changes.
VLAN, ACL, firewall, or DHCP changes can interrupt service without any device configuration changes.

Fix

Confirm the device is powered and linked to the network (link/activity LEDs).
Click Discover and wait until the status shows 100% completion.
Verify the PC and device are on the same physical LAN.
If separated by a router/firewall, run WinDiscovery from a PC inside the remote LAN, or configure the router/firewall to pass bi-directional UDP broadcasts on 6163.
Some environments also require UDP ports 6165, 6166, and 6264.
Verify your switch supports the device link speed.
If discovery is still unreliable, use an alternate configuration method (SSH/Telnet where supported).

Article ID: KB-NET-007
KB Version: