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

    • Direct messaging is finally making its way to Threads by David Uzondu Meta has announced it will finally begin testing direct messages on Threads, claiming that it was a "top request" since the platform's big splash in July 2023. This has been a massive pain point for users. For nearly a year, attempting to have a private conversation meant awkwardly fumbling over to a linked Instagram account, which for some people, completely killed the experience of actually using the app. Head of Instagram Adam Mosseri acknowledged this, stating "we know how important messaging is" to the platform's mission. It makes sense; a social network without a private messaging feature feels incomplete, especially when it is trying to supplant X. The initial test for this overdue feature is now rolling out to a limited number of people in Hong Kong, Thailand, and Argentina, with a wider release planned for later. For serious users and creators who hate having to send people to other apps like Instagram for DMs, this is fantastic news. For others, it's just one more inbox to check. Users included in the test will spot a new envelope icon on the main navigation bar, located at the bottom on mobile and on the left-side menu on the desktop site. The company, in typical fashion, has not offered a concrete timeline on when everyone else gets access, only saying it will expand "soon". In related news, Threads recently migrated its web presence from the old threads.net address to the much cleaner threads.com domain. That old domain was a leftover from the launch because Meta did not actually own the .com version, which was later scooped up. This change came alongside a cluster of other improvements to the web app, including a pop-up post composer that follows you as you scroll and provides easier access to your saved and liked posts.
    • Generally, Earth never initiated that animals lay straight
    • Several UI improvements masquerading as a major update. I'm truly hating this trend.
    • OpenAI to use Google Cloud despite rivalry, diversifying beyond Microsoft by Paul Hill To help it meet its massive computing demands for training and deploying AI models, OpenAI is looking into a surprising partnership with Google Cloud to use its services. It was widely seen that OpenAI was Google’s biggest threat, but this deal puts an end to the idea that the pair are purely competing. The two companies haven’t made any public announcement about the deal but a source speaking to Reuters claimed that talks had been ongoing for a few months before a deal was finalized in May. Notably, such a deal would see OpenAI expand its compute sources beyond Microsoft Azure. Microsoft had arrangements in place with OpenAI since 2019 that gave it the exclusive right to build new computing infrastructure for the startup. This limitation was loosened earlier this year with the announcement of Project Stargate. OpenAI is now allowed to look elsewhere for compute if Microsoft is unable to meet the demand. A win for Google Cloud, a challenge for Google's AI strategy The deal will see Google Cloud supply computing capacity for OpenAI’s AI model training and inference. This is a big win for Google’s Cloud unit because OpenAI is a massive name in AI and it lends credence to Google’s cloud offering. It also justifies Google Cloud’s expansion of its Tensor Processing Units (TPUs) for external use. On the back of the news, Alphabet’s stock price rose 2.1%, while Microsoft’s sank 0.6%, showing investors think it’s a good move for Google too. While many end users don’t interact with Google Cloud the same way they do with something like Android or Chrome, Cloud is actually a huge part of Google’s business. In 2024, it comprised $43 billion (12%) of Alphabet’s total revenue. With OpenAI as a customer, this figure could rise even more given the massive amounts of compute OpenAI needs. By leveraging Google’s services, it will also give OpenAI access to the search giant’s Tensor Processing Units (TPUs). Unlike GPUs, these chips are specifically designed to handle the kinds of calculations that are most common in AI and machine learning, leading to greater efficiency. Google’s expansion of these chips to external customers has already helped it attract business from Anthropic and Safe Superintelligence. While Google will happily take OpenAI’s money, it needs to tread carefully giving compute power to a rival, which will only make OpenAI more of a threat to Google’s search business. Specifically, it’ll need to manage how resources are allocated between Google’s own AI projects and its cloud customers. Another issue is that Google has been struggling to keep up with the overall demand for cloud computing, even with its own TPUs, according to its Chief Financial Officer in April. By giving access to OpenAI, it means even more pressure. Hopefully, this will be short lived as companies compete to build out capacity to attract customers. OpenAI's push for compute independence Back in 2019 when Microsoft became OpenAI’s exclusive cloud partner in exchange for $1 billion, the AI landscape was much different. End users wouldn’t have access to ChatGPT for another 3 years and the rate of development of new models was less ferocious than it is today. As OpenAI’s compute needs evolve, its relationship with Microsoft has had to evolve too, including this deal with Google and the Stargate infrastructure program. Reuters said that OpenAI’s annualized run rate (the amount they’ll earn in one year at its current pace) had surged to $10 billion, which highlights its explosive growth and need for more resources than Microsoft alone can offer. To make itself more independent, OpenAI has also signed deals worth billions of dollars with CoreWeave, another cloud compute provider, and it is nearing the finalization of the design of its first in-house chip, which could reduce its dependency on external hardware providers altogether. Source: Reuters
    • I don't think that means what you think it means
  • Recent Achievements

    • Enthusiast
      computerdave91111 went up a rank
      Enthusiast
    • Week One Done
      Falisha Manpower earned a badge
      Week One Done
    • One Month Later
      elsa777 earned a badge
      One Month Later
    • Week One Done
      elsa777 earned a badge
      Week One Done
    • First Post
      K Dorman earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      535
    2. 2
      ATLien_0
      272
    3. 3
      +FloatingFatMan
      201
    4. 4
      +Edouard
      200
    5. 5
      snowy owl
      138
  • Tell a friend

    Love Neowin? Tell a friend!