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.

  On 26/09/2012 at 16:23, BudMan said:

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.

  On 26/09/2012 at 16:29, Chris123NT said:

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?)

  On 26/09/2012 at 17:01, hjf288 said:

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.

  On 26/09/2012 at 16:29, Chris123NT said:

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

    • The new official logo of the GOP
    • Linux 6.16-rc1 is out: What's new and what does it mean for your system? by Paul Hill Linus Torvalds, head and founder of the Linux kernel, has announced the closure of the merge window where major new features are added to the kernel, and the beginning of the Linux 6.16 release candidates, beginning with release candidate 1 (Linux 6.16-rc1). Linux 6.15 was released two weeks ago and in the time since, developers have had the opportunity to try and get their new kernel features into the Linux 6.16 kernel. Over the next two months, we will get seven or eight release candidates where developers will stabilize new and existing features. This means that the stable version of Linux 6.16 will arrive around the end of July. Torvalds said that the merge window seemed pretty normal this time, but did say he had a feeling that there were more “late straggler” pull requests than is typical. Despite this, everything seems to be fine and the schedule will be going forward as planned. Key areas of development Torvalds explained that around half of the changes in the first release candidate were driver updates, with the bulk of those being made up with by GPU and networking drivers. For end users these are the most important changes because when your favorite distribution of Linux ships a new release with this kernel, it will support more graphics cards and networking equipment like Wi-Fi cards. The non-driver updates in this version are split between architecture-specific updates, documentation and tooling (perf tool and selftests), and core changes to filesystems, core kernel, memory management, and networking. Torvalds said the core changes include some of the “most important” changes, though they’re not necessarily major changes. Fixes to the core ensure a more stable Linux kernel for end users, plus better performance. The merge window saw developers submit thousands of non-merge commits and merges. The non-merge commits were around 13,000 while the merge commits nearly reached 1,000. There were 1,783 unique authors submitting code during this window. Next steps Over the coming weeks, Linux developers, including individuals or representatives of companies, will submit bug fixes for new and existing features. This release candidate cycle will run until around the end of July and then the final version will become available. End users shouldn’t go out and download Linux 6.16 when it’s released, instead just wait for your Linux distribution to update to it, as distribution-specific changes get made. Neowin will be following these releases and reporting on any interested changes that are noted. Source: LKML
    • There was no cancelation. Microsoft delayed work on it to focus on further tuning the OS and improving the OS experience overall, before going full core into a direct hardware battle with their partners.
    • As someone who has 500+ hours of playtime on Anno 1800, all I can say is shut up and take my money.
  • Recent Achievements

    • Week One Done
      Al_ earned a badge
      Week One Done
    • Week One Done
      MadMung0 earned a badge
      Week One Done
    • Reacting Well
      BlakeBringer earned a badge
      Reacting Well
    • Reacting Well
      Lazy_Placeholder earned a badge
      Reacting Well
    • Dedicated
      Epaminombas earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +FloatingFatMan
      273
    3. 3
      ATLien_0
      242
    4. 4
      snowy owl
      210
    5. 5
      Edouard
      182
  • Tell a friend

    Love Neowin? Tell a friend!