I'm an infant in the world of traffic prioritization so I apologize if I'm completely barking up the wrong tree here. One of my managers has began working from home and is using Remote Desktop a good bit. The connection here at the office is through Comcast (6 mbps down, 768 kbps up). We do not host any public servers. Thus, that's plenty of bandwidth for RDP, but she is seeing quite a bit of lag. I'm sure some of it is coming when our salesmen and engineers send out various cad drawings and pdfs via e-mail, sucking up all the upstream bandwidth and leaving her connection floundering. Obviously the lag she sees could also be coming from areas beyond my control, but I'd like to do what I can on my end to be sure she can get what she needs.
Beyond the basic tweaks to the PCs and Remote Desktop, one part of the solution would be to put a high priority on remote desktop traffic. I *assume* QoS can handle this.
Consider for the moment the office PC, the switch, the router, and the firewall: For QoS to be properly utilized, will I want QoS to be supported and configured at every step in that chain, or will having a switch and PC that supports QoS be sufficient to get that traffic prioritized?
Beyond the basic tweaks to the PCs and Remote Desktop, one part of the solution would be to put a high priority on remote desktop traffic. I *assume* QoS can handle this.
Consider for the moment the office PC, the switch, the router, and the firewall: For QoS to be properly utilized, will I want QoS to be supported and configured at every step in that chain, or will having a switch and PC that supports QoS be sufficient to get that traffic prioritized?
Facebook
Twitter