Knowledge Base / Network / Remote Support Session Troubleshooting
Problem
A support technician cannot connect to a remote session, screen sharing fails, or the remote control tool disconnects during troubleshooting.
Session failures are often caused by firewall rules, weak connectivity, missing permissions, or a change in user accounts. Verify the connection path before restarting the entire workflow.
Symptoms to check
- Remote tool says the session cannot be established or the user is not ready.
- Connection drops during screen sharing or remote control.
- Only certain users or locations are affected.
Possible causes
- Firewall, VPN, or network filtering is blocking the tool.
- The user lacks permission to start or join the session.
- Poor bandwidth or network instability is breaking the live connection.
Resolution
- Check whether the user is online, signed into the correct account, and connected to the expected network or VPN.
- Confirm the remote support tool is approved and not blocked by the local firewall, endpoint policy, or proxy settings.
- Review whether the issue is limited to one device or affects multiple users in similar locations before making a broad change.
- Restart the support tool, refresh the inbound connection, and retry the session using a fresh invite or session ID if the prior connection was interrupted.
- If the tool remains unstable, collect the error message, network status, and whether the issue occurs with screen share or remote control only, then escalate to infrastructure or security support.
Prevention and preparation
- Keep approved support tools and VPN access paths configured for remote assistance.
- Confirm device and network permissions before remote sessions begin.
- Document which proxies, VPNs, and firewalls commonly affect remote support sessions.
Related guides
Still not fixed? Escalate with the user location, session ID, current network status, and the exact message seen during the failed connection.
Submit a ticketLast reviewed: October 2026