Troubleshooting · 6 min read
Why a remote session keeps disconnecting, and how to stabilise it
Written for: IT staff and support operators whose remote sessions drop mid-work and need to identify the cause rather than keep reconnecting.
In short
Sessions that drop repeatedly usually have one of four causes: an unstable network link, a power setting suspending the adapter or the machine, an idle or policy timeout ending the session deliberately, or Wi-Fi roaming between access points. The pattern of the drops tells you which. Random drops point at the network, drops at a consistent interval point at a timeout, and drops when nobody is typing point at power or idle settings.
Key takeaways
- Timing is your best diagnostic. Regular intervals mean a timeout; irregular drops mean the network.
- Sleep, hibernate and selective suspend on the network adapter end sessions silently and look like network faults.
- Wi-Fi roaming between access points breaks long-lived connections that a wired link would survive.
- Idle timeouts are often deliberate policy, not a fault — check before you chase a bug that does not exist.
- Reconnecting repeatedly hides the pattern. Log the drop times before you change anything.
Read the pattern before changing anything
Write down the times of the last five drops. If they cluster at a consistent interval — every fifteen minutes, every hour — something is ending the session on purpose, and you are looking for a timeout in the tool, the operating system, or a firewall's session table. If the gaps are irregular, the link itself is unstable.
This one habit converts an infuriating intermittent fault into a short list of candidates. Reconnecting immediately each time, which is the natural instinct, destroys the evidence.
Power management, the silent killer
Windows will suspend a network adapter to save power, and will sleep a machine that it believes is idle — and a remote session does not always count as activity, particularly when the operator is reading rather than typing. The symptom is a session that dies while you are thinking, and a device that reappears moments after someone moves the local mouse.
On any machine intended for unattended access, disable adapter power saving and set the sleep timers to never. Laptops need this checked on both the battery and mains profiles, because they differ.
- Adapter properties: turn off 'allow the computer to turn off this device to save power'
- Power plan: sleep and hibernate set to never on machines that must stay reachable
- USB selective suspend, which can affect docked network adapters
- Fast startup, which can leave the network stack in an odd state after a shutdown
Network instability and Wi-Fi roaming
A remote session is a long-lived connection, which makes it far more sensitive to brief interruptions than web browsing. A page load that stutters for two seconds is invisible; a session that stutters for two seconds may drop.
Wi-Fi is the usual offender. A laptop moving between access points, or sitting at the edge of coverage and flapping between two, will break long-lived connections repeatedly while a browser appears fine. Test the same work over a wired connection: if the drops stop, you have your answer and the fix is a network problem, not a software one.
Deliberate timeouts
Some drops are the system working correctly. Idle session timeouts, maximum session durations, and firewall session-table expiry all exist for good reasons, and security policy may require them. Check the configured limits before treating a clean, predictable disconnection as a defect.
Where the timeout is a firewall's rather than the tool's, the fix is usually to allow the connection's keepalives through rather than to extend the timeout indefinitely.
Common mistakes
- Changing several settings at once, so you never learn which one mattered.
- Blaming the remote tool for a Wi-Fi problem that a wired test would have identified in two minutes.
- Leaving sleep enabled on unattended machines and rediscovering the same fault every few weeks.
- Extending every timeout to its maximum, which trades a support annoyance for a genuine security weakness.
Frequently asked questions
- Why does my session drop at exactly the same interval each time?
- A consistent interval means something is ending the session deliberately — an idle timeout, a maximum session duration, or a firewall expiring the connection from its session table. Look for the configured limit that matches the interval.
- Why does the session drop when I stop typing?
- Idle detection, or the remote machine going to sleep. A session where the operator is reading rather than interacting can look idle to both the tool and the operating system's power settings.
- Does Wi-Fi cause remote session drops?
- Frequently. Roaming between access points and marginal signal both break long-lived connections while leaving ordinary browsing apparently fine. Testing over a wired link is the fastest way to confirm it.
- Should I just increase the timeout?
- Only if you know which timeout is firing and why it exists. Raising a security-driven idle limit to stop an inconvenience is a poor trade; fixing a flapping wireless link is not.
How this works in 247connect
247connect sessions reconnect automatically when the underlying link recovers, which keeps a brief network interruption from ending the work — though it does not remove the need to fix a genuinely unstable connection.
More troubleshooting guides
Black screen in a remote session
Why a remote session connects but shows only a black screen, covering the secure desktop, graphics drivers, headless machines, multi-monitor states and display capture permissions.
Slow or laggy remote session
Diagnosing a sluggish remote session: separating latency from bandwidth, the effect of resolution and colour depth, wireless links, and the settings that make the largest practical difference.
Agent offline after a reboot
Why an unattended device fails to come back after restarting, covering service start types, boot ordering, BitLocker and login-gated networks, fast startup and dependency failures.