Your Remote Desktop Services session has ended (network problem) Networking Origin: Network OSI layer 5 · Session Last updated 5 Nov 2026

Networking: Your Remote Desktop Services session has ended. Possibly the network connection was lost / Remote Desktop disconnected, error code 0x904

An established Remote Desktop session dropped because the network under it stalled or the session was reset.

Exact message you may see Your Remote Desktop Services session has endedPossibly the network connection was lostRemote Desktop disconnected error code 0x904Your Remote Desktop session has ended. Possibly, the network connection was lostThis computer can't connect to the remote computer 0x904
Explore the map of this error Full error map →
Seen on: Windows Networking

Meaning

Look for Wi-Fi roaming, VPN reconnects, MTU problems or firewalls that cut idle sessions. Enable keep-alive on the RDP client/server, use UDP transport or reduce bandwidth settings, check the session limits in Group Policy, and review event 40 in the TerminalServices-LocalSessionManager log.

Common causes

  • Unstable Wi-Fi or VPN underneath
  • Firewall/NAT idle timeout dropping the TCP session
  • MTU/fragmentation problems on the VPN
  • Server idle/disconnect session limits
  • Packet loss or high latency

⚡ Quick fix

  1. Use a wired connection or stable VPN
  2. Enable keep-alives (Group Policy: Configure keep-alive connection interval)
  3. Lower the VPN MTU and allow RDP UDP 3389

Detailed fix by platform

Windows

  1. powershell
    eventvwr.msc   # Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager
Test-NetConnection server -Port 3389

How to diagnose

  1. Underlying link — Stable?
  2. Keep-alive — Enabled?
  3. Limits — Session timeouts set?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

0x80070035 — 0x80070035: The network path was not found (System error 53) (Windows)0x80070035169.254.x.x self-assigned IP (DHCP failed) — Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP (Networking)169.254.x.x self-assi…Connections hang on large transfers (PMTU black hole) — Networking: SSH/HTTPS connects but hangs on large data — path MTU discovery black hole (Networking)Connections hang on l…Idle connections silently dropped by firewall/NAT — Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive) (Networking)Idle connections sile…NO_PROPOSAL_CHOSEN (IPsec/IKE) — Networking: IKE: received NO_PROPOSAL_CHOSEN — IPsec peers can't agree on encryption, hash or DH group (Networking)NO_PROPOSAL_CHOSEN (I…The specified network name is no longer available (64) — Networking: Windows error 64: The specified network name is no longer available — SMB session dropped (Networking)The specified network…Windows: Default gateway is not available — Networking: Windows: Default gateway is not available / Diagnose Connection Problems: DHCP not enabled (Networking)Windows: Default gate…WireGuard: Handshake did not complete after 5 seconds — Networking: Handshake for peer did not complete after 5 seconds, retrying (try 2) — WireGuard tunnel never establishes (Networking)WireGuard: Handshake …Your Remo…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.