Delay in Remote Desktop Connection. What are possible solutions?


Recommended Posts

I am experiencing delays and reconnecting issues when connecting to RDP. Both wired and wireless.

I have purchased a new router - Linksys EA3500 - and still these issues occur.

Ping tests stated around 18ms for my connection.

My internet speeds/subscription are 120 MB down, 10 MB up. I have tested with different "Experience / Performance" settings within RDP, from low-speed broadband to high-speed broadband; all without success.

I have KIS2013 installed with default settings on both computers (wired and wireless).

What can be the issues for these delays/secs of 'hickups' during the RDP-connection?

RDP connections to where? Some box on the internet, or between boxes on your own network - wired to wireless, wireless to wireless, wired to wired?

Also what do you consider delay, 2 seconds, 5 seconds, 10, 20, 3 minutes?

RDP to some box (server) on the internet - our server 80 km away.

The server is wired to its backbone/Internet, I make a RDP-connection via my computer (wired) or notebook (wireless) from home (or elsewhere) - I use its name/alias and not the IP.

The delay is a couple of seconds (mostly 2-5 sec); screen 'freezes', reconnecting popups appears, connection is back again and I can start working again...

And this once every 2-5 minutes.

EDIT:

adjusted delay time to real circumstances

well there could always be a slight delay in resolving to its FQDN, I think that is what you meant by name/alias because those are not resolvable on the internet but a fully qualified domain name is ;) something.something.tld

so you its not really a delay in connection, but a loss of connection and reconnect

"this once every 2-5 minutes."

Are you connecting via a VPN to this server, or just the normal RDP 3389 just over the internet? Is there any firewall on the other end limiting connections to this port to only where your coming from?

You put 3389 open on the public internet and its going to get hit quite often with people attempting to log in.

If your saying it happens every few minutes I would look at logs on server side for any hints, and also would sniff the traffic from your connection. This will show you if your getting a lot of retransmission on lost packets, etc.

lagging could be upstream not fast enough to handle request, could be dns not fast enough to handle name resolution...you mention your upstream, is your upstream the upstream at home or your upstream at the office. The upstream at the office needs to be ~1Mb/s for optimal response...your down stream at home needs to be at least that. Also the dns plays quite a bit into speed, try connecting to the ip to negate dns being an issue. if it is fast connecting to the outside ip, then the issue is dns related.

it's kinda strange... when I use my cell phone with tethering (wayyy slower connection, everything is ok) on the same notebook, I have a good connection and no delay/lag.

It seems that either my modem or router is the "bad kid in town".

I just got a new router today - default settings - so that should not be the issue.

I might just check a direct cable connection from my modem to my computer (thus cancelling out the router) and see what happens...

I'll come back to this latter thing.

@ +Chris13NT, how can I prevent this? Or is this ISP-related?

Just tested it "quick and dirty" and the delay/lag is not present when connecting directly to the modem.

When I put my router in between the lag is there yet again.

There is a power/surge adapter to prevent over-voltage, but this hasn't been an issue ever since.

Might it be cable related? And that one of the UTP-cables has been damaged/is broken?

Replacing might help, but that I need to get myself some new cables....

By the way, the current cable-setup is:

ISP-entrance in my home - cable to modem, provided bij ISP - modem - cable to surge-adapter - cable to router, from there the standard 4 GBit ports of this EA3500 to computer and other periphicals + router wireless to notebook and other periphicals.

What is your dns configuration when connection directly to the modem?

start, run, cmd

ipconfig/all

What is your dns configuration when connected to the router?

start, run, cmp

ipconfig/all

change the dns on your adapter to the dns that you are getting when you are on the modem. does the same problem exist?

dns could be the problem on initial delay, or just failure to resolve - but once the connection is established and having freezes every few minutes does not seem like a dns related problem to me.

What kind of router is it? Some routers have trouble with connections over 50mbit, I had a Linksys E3000 and it couldn't cope with my 85mbit FiOS line, it would crap out every time I pegged the download.

It could be cable related but I doubt it.

I have a brand new Linksys EA3500. It should get "Transfer rates up to 300 + 450 Mbps".

The DNS I get when connect to the router is 1 IP: 192.168.1.1

When directly connected to the modem DNS server is 2 IP's: 213.48. .... and 62.179. ...

yeah those are from your ISP when connected to modem, and when connected to router your using it as your dns forwarder. This is a common setup, your router would then forward dns to those handed to your router via your ISP 213.48 and 62.179

But again if your having the issues once your connected, it seems highly unlikely that it would be dns related.

yeah those are from your ISP when connected to modem, and when connected to router your using it as your dns forwarder. This is a common setup, your router would then forward dns to those handed to your router via your ISP 213.48 and 62.179

But again if your having the issues once your connected, it seems highly unlikely that it would be dns related.

Thx. So what can it be?

unlikely sure, test it, verify it, make sure. be sure, not be somewhat sure....perhaps the router is being retarded when forwarding, it is a link in the chain....remove the link.

I thought it was initial connection....if it is not initial connection, then it is not dns related. something is happening with the traffic when it goes from router to modem.

Can you to a trace route to the IP of the RDC server? This might give a clue if you have a hop with unusually high ping.

do tracert <ip (or dns name)> in cmd

The fact that the lag only happens when the router is in the link is making me almost positive it's the router botching things.

Can you to a trace route to the IP of the RDC server? This might give a clue if you have a hop with unusually high ping.

do tracert <ip (or dns name)> in cmd

In which setup and from where?

From my computer, connected via router, to the RDC server?

Or from the RDC server to my computer? (and also here via router or directly connected to modem?)

Off topic but in reply to Chris, my e2000 handles my 120mbit line with ease and it has a slower CPU than your e3000..

So something is up there..

It could have just been going bad, or it could have been DD-WRT's fault.

Can you to a trace route to the IP of the RDC server? This might give a clue if you have a hop with unusually high ping.

do tracert <ip (or dns name)> in cmd

The fact that the lag only happens when the router is in the link is making me almost positive it's the router botching things.

What kind of info do you need from this trace?

From which hop# there is a time out? or else?

There has been some less delays (but still annoying) with the new FW... although I had to wrestle myself through the Cisco Cloud Connect.

Still some delays.

Question remains....

EDIT:

I guess I was over-enthusiastic... delays still remain as strong as before :(

This topic is now closed to further replies.
  • Posts

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!