Problems with Virtual Machine Remote Control clients

Problems with Virtual Machine Remote Control clients

Whenever I use Virtual Server's Virtual Machine Remote Control clients, I have a number of problems with the remote machine lagging or repeating keystrokes or not responding to mouse movements. What can I do about this?

    Requires Free Membership to View

    When you register, my team of editors will also send you the latest expert resources covering all areas of server virtualization, such as platforms, architectures and strategies, server hardware, managing virtual environments, application issues and more.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchServerVirtualization.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchServerVirtualization.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The VMRC client is only one of several possible ways you could connect to a virtual machine. My personal favorite way to do this is just to set up a remote desktop client (RDC) connection, which is built into Windows and works as transparently with virtual servers as it does with a real remote computer. VMRC uses its own protocol which is deliberately distinct from RDC, and which has been engineered to allow multiple users to connect to the same virtual machine transparently. If you're only using one connection at a time to administer virtual machines, use RDC instead; it'll be a little smoother.

This was first published in August 2006