Symptoms
- Devices appear in WinDiscovery but configuration changes fail
- Firmware update or programming operations fail, time out, or do not start
- Discovery works, but device control functions do not
Causes
- Firewall rules allow discovery but block additional UDP ports required for control or update operations
- Security policies prevent firmware programming traffic across VLANs
- Control or programming traffic is blocked even though discovery traffic is allowed
Suggested solutions or troubleshooting steps
- Confirm whether the failure is discovery-only or control-only.
If discovery works but control fails, focus on firewall and port permissions for control and programming functions. - Test from a PC on the same subnet as the device.
If control works on-subnet but fails across VLANs, your network is likely blocking control or programming traffic between segments. - Ask IT to allow the required control and programming traffic.
Provide IT with the port and protocol requirements for WinDiscovery control and firmware programming features. - Use direct device management where applicable.
If policy prevents remote programming, manage the device through approved methods on the local subnet.
Fix verification
- Configuration changes apply successfully and persist after refresh or reboot
- Firmware update operations complete successfully when permitted by network policy
Article ID: KB-WINDISC-004
KB Version: