Virtual Machine Remote Control Client gets "No Connection"

Virtual Machine Remote Control Client can get “no connection” for several reasons:

You have not enabled VMRC, do this under the server properties tab of the admin console
You have the wrong URL
You have the wrong port (default is 5900)
You do not have vmrc:// at the beginning of the url
You really don't have permissions or your user account or password is incorrect
You are disconnected from your domain and for some reason the cached credentials don't always cut it. (try a local admin account)
Your DCom settings are wonky

open Dcom config, find “virtual server“ and begin to relax the settings. Allow local and remote access for all authenticated users etc (use this one carefully people, you might open the door a little too wide)

Share This Post:

posted on Thursday, April 13, 2006 8:48 AM

Feedback

# re: Virtual Machine Remote Control Client gets "No Connection" 9/5/2007 9:14 AM Charlie Markwick

I am seeing the no connection happening only after a connection times out. To be able to remote control again I have to reboot the host server. Have you seen his?

# re: Virtual Machine Remote Control Client gets "No Connection" 11/1/2007 9:02 PM eddy

set the correct TCP/IP address in the Virtual Machine Remote Control (VMRC) Server Properties.

# re: Virtual Machine Remote Control Client gets "No Connection" 11/5/2008 3:04 PM Adam M. Casgar

Just wanted to add one last thing to check...if you are running Server 2008 you need to check the Windows Firewall settings and add an exception for port 5900 (VRMC)

# re: Virtual Machine Remote Control Client gets "No Connection" 3/23/2009 8:53 AM Rob Waite

Adding port 5900 in the firewall execption worked a treat for me

# re: Virtual Machine Remote Control Client gets "No Connection" 8/20/2009 5:01 AM val

Trick is set ip in vmrc properties to all unassigned. Dah!!!!!!!!!!!!

# re: Virtual Machine Remote Control Client gets "No Connection" 10/14/2009 10:41 AM pcwally

Thanks val! This was driving me nuts!

# re: Virtual Machine Remote Control Client gets "No Connection" 2/19/2010 8:35 AM FeeLz

if you access VMRC on Workstation and receive "No Connection" and if your Virtual Server installed on Windows Server 2008
Access Windows Firewall on Windows Server and open port 5900
Return to workstation and try again!

Neil Thompson

News

Article Categories

Archives

Post Categories

Fav BizTalk Blogs

Feedback