Member Avatar for edek

I have network with one router and two computers connected to it (one through wireless connection). I can create 'Remote Desktop Connection' from one computer to other but connection is broken after a few seconds.

Ideas?

  • 7 Contributors
  • 11 Replies
  • 2K Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by zelkea

Dani AI

Generated

If file shares are stable but RDP drops after 3-5 seconds on the Wi‑Fi machine, the issue is likely transport or Wi‑Fi behavior rather than basic IP. Since Windows 8 and later prefer RDP over UDP, try forcing TCP only to rule out flaky UDP handling in some home routers/APs. On the host, set Group Policy: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Select RDP transport protocols = Use only TCP. Or, on the client, disable UDP:

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" ^
 /v fClientDisableUDP /t REG_DWORD /d 1 /f

This is a safe isolation step; if it stabilizes sessions, you can leave it in place. (learn.microsoft.com)

Next, collect evidence. While reproducing the drop, watch Event Viewer on the target: Applications and Services Logs > Microsoft > Windows > TerminalServices‑LocalSessionManager and TerminalServices‑RemoteConnectionManager. These logs surface protocol errors (for example, TermDD event 50), licensing faults, or session arbitration causing the disconnects that look like "another user has connected." They are far more precise than the generic client popup. (learn.microsoft.com)

If the Wi‑Fi PC is the one being remoted into (as noted), update its wireless driver/firmware and test with a wired cable as a control. Avoid relying solely on Device Manager’s "Allow the computer to turn off this device to save power" for Wi‑Fi; that checkbox mainly affects sleep/resume and not runtime Wi‑Fi power behavior on many adapters. Use a balanced or high‑performance power plan instead and confirm the adapter’s vendor power settings. (learn.microsoft.com)

If disconnects persist, consider enabling RDP keep‑alives at 1–5 minutes to mitigate aggressive middlebox timeouts (not a cure for sub‑minute drops, but helpful in noisy networks). Policy: Configure keep‑alive connection interval. (learn.microsoft.com)

These steps complement ’s Experience‑tab tweak by targeting transport and logging so you can pinpoint the root cause rather than just masking bandwidth.

Recommended Answers

All 11 Replies

Member Avatar for TheNNS

what is the lease time for ip addresses? how long does it last

Member Avatar for edek

I do not use dhcp :)
Any other ideas?

I would also say that after trying to connect to the computer that uses wireless connection through Remote Desktop it breaks the connection after a few seconds (computer or router breaks it) (Why?) . And that is the main problem here.

I use shared resources of that computer without problems.

Member Avatar for WebDave

Do you get a continuous connection after doing a Remote Desktop and for how long?

Member Avatar for edek

Do you get a continuous connection after doing a Remote Desktop and for how long?

I can connect for about 3-5 seconds - I mean I can move the "mouse" pointer on remote desktop for a while and then I cant - it stops responding and the info appears saying that connection was lost.

Member Avatar for ibm650

I have the same problem - only on 2 pcs, one was just rebuilt and the other is new, so I think it is perhaps a MS problem, remember the remote desktop was recently one of the updates.

Member Avatar for TheNNS

why don't you all just try using realvnc or ultravnc? these are far better from remote desktop

Member Avatar for TaryxJohn

We experienced a similar problem. An outside partner was connecting via Remote Desktop with 5 separte sessions. Their sessions were inconsistently freezing, sometimes in a few seconds, other times after several minutes.

Turns out they altered the remote desktop shortcut setting we sent them and changed the Experience tab to Lan (10Mbps or higher) instead of the Modem (56 Kbps). Hope this helps.


-John

Member Avatar for ibm650

We experienced a similar problem. An outside partner was connecting via Remote Desktop with 5 separte sessions. Their sessions were inconsistently freezing, sometimes in a few seconds, other times after several minutes.

Turns out they altered the remote desktop shortcut setting we sent them and changed the Experience tab to Lan (10Mbps or higher) instead of the Modem (56 Kbps). Hope this helps.


-John

Thanks, but did not work
I get the another user has connected, and I am the only one using the machines.

Member Avatar for DaleEMoore

I can connect for about 3-5 seconds - I mean I can move the "mouse" pointer on remote desktop for a while and then I cant - it stops responding and the info appears saying that connection was lost.

I am experiencing something similar and wonder if you found a solution to your problem? I am disconnected after 30 seconds.

Member Avatar for edek

I am experiencing something similar and wonder if you found a solution to your problem? I am disconnected after 30 seconds.

I'm sorry, but I have not solved it. Actually I've set up Linux on all my computers and now everything works fine;)

Member Avatar for zelkea

The problem could be as simple as limited bandwith over your wireless connection. On your RDP windows I would drop your connection speed to Modem and see if it makes a difference. You can do this by Options -> Experience -> change this to Modem.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.