Help
Check the local network before you troubleshoot deeper
Most discovery problems have a simple network cause. This page keeps the checklist short and practical.
Local network checklist
Run through these checks first whenever machines cannot see each other or input flow never starts.
- Put both computers on the same local subnet when possible.
- Check that local firewall rules are not blocking ViewMeld traffic.
- Avoid guest Wi-Fi networks that isolate devices from each other.
- Test basic reachability between machines before troubleshooting the app itself.
- Re-pair devices after a major network or host identity change.
What this usually means in practice
The goal is to rule out network isolation before you assume the app itself is misbehaving.
Office guest Wi-Fi and segmented networks often block peer discovery even when both devices have internet access.
A newly installed firewall rule can stop local traffic even though the rest of the machine looks healthy.
If the machines can discover each other but pairing fails, the next step is usually the pairing guide rather than deeper network debugging.
If your desk setup changes often, save time by re-checking host approval and layout before you rebuild the whole configuration.
Keep your evaluation moving
These follow-up pages usually help once the network checks are done.
Trust
Security and privacy details
See how local-network pairing, allowed hosts, and direct connections keep the workflow simple.
FAQ
Questions before buying?
Review licensing, platform support, clipboard behavior, and common evaluation questions.
Help
Local network checklist
Make sure your machines can discover each other and move input traffic cleanly on the same network.