Symptoms
- Devices appear in WinDiscovery only when the PC is on the same subnet as the device
- No devices are discovered across VLANs, routed networks, or VPN connections
- Discovery works on a local bench network but fails on the production network
Causes
- Discovery traffic relies on UDP broadcast or multicast that is not forwarded by routers
- Firewall, ACL, or security policy blocks the UDP discovery traffic between subnets
- Network segmentation (VLANs) prevents broadcast-style discovery by design
Suggested solutions or troubleshooting steps
- Confirm the device’s IP address from an on-subnet PC.
If the device is reachable from a local PC, note the IP address and confirm basic connectivity. - Use WinDiscovery Discovery Options for unicast discovery (recommended).
In WinDiscovery, open Discovery Options and add the device IP address or IP range as a unicast discovery target (when supported by your version of WinDiscovery). - Ask your network administrator to permit the required UDP traffic between subnets.
If discovery must function across VLANs, routers and firewalls must be configured to allow the required discovery traffic. Many networks block this by default. - If discovery is not permitted across VLANs, use direct IP management instead.
If policy prevents discovery across subnets, manage the device by navigating directly to its IP address in a browser or by using approved unicast methods.
Fix verification
- The device can be discovered from the intended network segment using unicast discovery options, or
- The device can be managed reliably by direct IP access according to your network policy
Article ID: KB-WINDISC-002
KB Version: