Remote Desktop Connection bandwidth usage?

Click For Summary

Discussion Overview

The discussion revolves around the bandwidth usage of Remote Desktop Connection (RDC) in Windows and its impact on internet performance. Participants explore the potential causes of slow internet speeds when using RDC, including latency issues and the adequacy of current bandwidth. The conversation also touches on alternative remote desktop solutions and their performance compared to RDC.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested
  • Experimental/applied

Main Points Raised

  • One participant questions whether the RDC is bandwidth intensive, noting that their internet slows significantly when using it, despite having a 16mb/s download speed.
  • Another participant suggests that a 16mbps connection should be sufficient for RDC and proposes testing alternative remote desktop software like VNC to determine if the issue is related to bandwidth or the software itself.
  • A participant recalls having used RDC effectively in the past, implying that it may not inherently be a bandwidth hog.
  • One participant points out that the user may be limited to connecting through a server at the office, which could complicate the use of alternative software.
  • Another participant recommends trying Google Chrome Remote Desktop as a free alternative, sharing their positive experience with it even on low bandwidth connections.

Areas of Agreement / Disagreement

Participants express differing views on whether RDC is excessively bandwidth-intensive and whether the observed latency issues are due to bandwidth limitations or other factors. There is no consensus on the cause of the slow performance or the best solution.

Contextual Notes

Some participants mention intermittent connection issues that occur even with minimal network usage, suggesting that the problem may not solely be related to RDC or bandwidth. The discussion does not resolve the underlying technical issues or assumptions regarding network performance.

Who May Find This Useful

Individuals experiencing slow internet performance while using Remote Desktop Connection, those considering alternative remote desktop solutions, and users interested in optimizing their network settings may find this discussion relevant.

trollcast
Gold Member
Messages
282
Reaction score
13
Is the remote desktop client in windows really bandwidth intensive?

We get roughly 16mb/s down and 1mb/s up even at fairly peak times, however as soon as dad goes on his laptop to use his desktop computer back at the office the internet becomes horribly slow, it doesn't seem to be a speed issue more just like the connection has tonnes of latency?

I presume the desktop connection is eating through most of the availible bandwidth which is why the speed is still ok but its still laggy?

Would upgrading to fibre optic broadband maybe help? (My dads ISP contract is up in a couple of months) Or any settings on the router or desktop connection client that would help?
 
Computer science news on Phys.org
Here's some relevant information for you to read up on
http://social.technet.microsoft.com.../thread/5efbaaac-c45f-4520-a2b4-97dd7d2ff66e/

Something else must be going on. I would imagine that a 16mbps connection should be good enough for RDP. You'd be using a small fraction of that bandwidth. Try to use another Remote Desktop utility like VNC or something and see if you still have the same issue. Help narrow down if the issue was bandwidth or software.
 
RDC is a hog, but I remember using it just fine when I'd leave my computer on in the university dorms when I'd go home for break. That was a good ten years ago.
 
I don't think he can use other connection software as he has to connect to the server at the office first and then log into his desktop machine from the server.

It maybe a general connection issue as it seems to be doing it intermittently even when there's only 1 PC connected to the network, it'll load up a bit of the page and then stop, load a bit more, stop again and then load a bit more?
 
You might try, just as a free comparison, the Google chrome remote desktop sharing.

You need chrome on both ends, install the free add-on, start it on the destination, communicate the code number to the other end to type into the add-on there. The destination needs to confirm they want to keep this open every ten minutes.

I used that to deal with a support problem where they had less than a megabit DSL on their end. I was really surprised how responsive it was. All you have to do is keep that chrome window open and keep confirming on the far end, everything else is just like you have control of the console. Maybe this would give you a speed and reliability comparison.

There is supposed to be a completely different Google app that doesn't require the confirmation and the code, but every time I try to download that I get a page won't load. Maybe Google dropped that.
 

Similar threads

Replies
1
Views
3K
Replies
31
Views
5K
Replies
4
Views
4K