What's new 
Some of our Android tablets connect to Hexnode Remote View/Control quickly, but others take a long time to scan or fail to connect. The devices are on different Wi-Fi networks and some locations have stricter firewall/security filtering enabled. Has anyone seen Remote View behave differently depending on the network? Trying to figure out if this is a device-side issue or something the network team needs to allow.
7 Views
Replies (2)
Marked SolutionPending Review
Hexnode Expert
2 days ago
Jun 16, 2026
Marked SolutionPending Review
Yes @shirleyc, Remote View/Control performance can vary based on network connectivity, firewall rules, antivirus filtering, or DNS/security filtering services such as Cisco Umbrella.
For Android Remote View/Control to work reliably, ensure that the corporate firewall allows the required Hexnode Remote View/Control communication. The commonly required ports are:
- Port 443 TCP: Used for the secured connection between the device and Hexnode.
- Port 3478 TCP and UDP: Used for signaling and data transfer.
- Port 5349 TCP: Used for secure signaling.
In addition to these ports, the required Hexnode domains and URLs should be allowlisted based on the Hexnode architecture and ports/URLs whitelist documentation.
If only devices on certain networks are affected, the issue is usually network-specific rather than a device policy problem. Testing the same device on a less restricted network can help confirm this.
Best Regards,
Isabel Lora
Hexnode UEM
Marked SolutionPending Review
Participant
2 days ago
Jun 16, 2026
Marked SolutionPending Review
That matches what I’m seeing. Devices on one courthouse network connect fine, but another location is inconsistent. We also have web filtering active there, so I’ll have the network team check the ports and allowed domains.
Save