WinDiscovery cannot discover the device

Symptoms

The device does not appear after a WinDiscovery discovery cycle completes.

Possible causes

• The device has no power or Ethernet link.
• The PC and device are on different network segments.
• Firewall or network rules block discovery traffic.
• The discovery cycle has not finished.

Troubleshooting steps

1. Confirm power and Ethernet link/activity indicators. Check that the switch supports the device link speed.
2. Run WinDiscovery from a PC on the same physical LAN as the device. Click Discover and wait for 100% completion before selecting a device.
3. Check that the PC and network allow WinDiscovery discovery traffic on UDP port 6163. For network-policy guidance, see Network ports and protocols for WinDiscovery and Masterclock applications.
4. If local discovery works but remote discovery fails, follow WinDiscovery cannot discover devices across subnets or VLANs.
5. If discovery remains unreliable, use an alternate management method only if the device supports it and network policy permits it.

Related articles

• WinDiscovery is blocked by Windows Firewall or endpoint security
• WinDiscovery status is intermittent or garbled

• WinDiscovery discovers devices but cannot configure or update them