Problems enabling Virtual Machine Remote Control (VMRC) server
Nina Chandler
operating systems (using win 2k3 R2) and Virtual Server 2005 R2.
Everything worked fine - and I used the VMRC to boot from the CD, and
install the Guest OS/ and enable RDP. Since then I been using the RDP to
carry on adding components to the Guest Virtual server.
Now I decided to revert back to accessing the Guest OS using VMRC instead of
RDP - but it wont let me.
I looked throgh my notes and try to reverse everything I did - but still no
joy.
When I try to re-enable the checkbox I am getting the following error
message:
Virtual Machine Remote Control (VMRC) server must be enabled before you can
remotely control a virtual machine with the ActiveX VMRC control or through
the Virtual Machine Remote Control client.
Also at the same time, I see the following three entries on the Error log:
Type Date/Time Category Message
3/16/2006
8:00:21 AM Setting Change The Virtual Server setting
"settings/remote_control/vmrc/enabled" was changed from true to false.
3/16/2006
8:00:21 AM Remote Control Virtual Server could not start the VMRC
server. Another server may be using the selected TCP/IP port.
3/16/2006
8:00:21 AM Remote Control This computer does not belong to an Active
Directory domain. Automatic authentication will always use NTLM
authentication.
3/16/2006
8:00:21 AM Setting Change The Virtual Server setting
"settings/remote_control/vmrc/enabled" was changed from false to true.
The Win2k3 server is set up on the host to use automatic IP / DNS. The Guest
is the same. There is a ADSL router on the network that provides the gateway
and DHCP. On the machine configuration I tried changing the default IP
settings (IP = 192.169.1.5 / or 'All assigned") and port setting (the
default 1024") - again to no avail.
NC
Steve Jain
wrote:
VMRC uses port 5900. Do you have another app running on the host,
like VNC, that uses port 5900?
--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
I am not employed of Microsoft.
Nina Chandler
VMC - but I do have a file with vmc extension - which I understand is the
VM. Could it be RDP? Which port does RDP use?.
So far this is all I got running on the host:
- Windows 2003 R2 with all the latest patches from Windows update
- Intel Network card teaming driver and app
- RAID monitoring app
- The Server management software that runs on a different port ..
- Java Virtual Machine [Needed for the above]
- Virtual Server 2005 R2
- And ofcourse it has RDP enabled My Computer / Properities
These are the things I got running on the Guest VM:
- Windows 2003 R2 with all the latest patches from Windows update
- VMAdditions
- RDP turned on in My Computer Properities
"Steve Jain" <noreply.-at-.essjae.com@> wrote in message
news:s95h1256ltdh39u1p...@4ax.com...
Steve Jain
wrote:
>I am not aware of anything that might use Port 5900 - and I am not running
>VMC - but I do have a file with vmc extension - which I understand is the
>VM. Could it be RDP? Which port does RDP use?.
>
>So far this is all I got running on the host:
>- Windows 2003 R2 with all the latest patches from Windows update
>- Intel Network card teaming driver and app
>- RAID monitoring app
>- The Server management software that runs on a different port ..
>- Java Virtual Machine [Needed for the above]
>- Virtual Server 2005 R2
>- And ofcourse it has RDP enabled My Computer / Properities
>
>
>These are the things I got running on the Guest VM:
>- Windows 2003 R2 with all the latest patches from Windows update
>- VMAdditions
>- RDP turned on in My Computer Properities
Actually, what I am talking about is VNC (Virtual Network Computing)
software, like RealVNC. It's a mostly platform independent remote
control solution. It was the what VMRC was originally based on and as
such both use port 5900.
A .VMC file is a configuration file for a Virtual Server VM. VNC and
a .vmc file are completely different. ;-)
RDP doesn't interfere with VMRC, at least not with the defaults of
both.
Since there's a log entry regarding VMRC and ports, that where I'd
start. You could try changing your VMRC port to some arbitrary number
and see if that resolves it.
Nina Chandler
and the guest have static IP addresses]. On the Machine Config I clicked on
the enable VMRC, and specified alternate ports - but to no avail.
Given that it worked before - I doubt it is a port issue.
Given that I can get it working with RDP, there is no compelling reason to
have VMRC. However, I still feel nervous about going to production where I
cant replicate the VMRC - just in case for what ever reason the RDP access
stop working.
I searched google and I found about half a dozen other cases where people
have had this issue - but noone has ever resolved this issue. Is there
anyone from Microsoft who is aware of an intermittent bug perhaps?
N
"Steve Jain" <noreply.-at-.essjae.com@> wrote in message
news:938h12deh0qlsi2np...@4ax.com...
Ben Armstrong [MSFT]
and tell me what you see?
--
Cheers,
Benjamin Armstrong
===============================
Virtual machine Program Manager
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Nina Chandler
now click on the little thumbnail - and I now have a choice of using either
RDP or VMRC.
Thanks for you help Ben and Steve.
NC
"Ben Armstrong [MSFT]" <ben...@online.microsoft.com> wrote in message
news:OP%23flJUS...@TK2MSFTNGP10.phx.gbl...
Balal Ahmad
i installed VNC server and after it uninstall it but Remote control client not connecting ?
Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com
Niels Immink
Not sure what is wrong with your setup but here's something you cold try:
- Change the VMRC tcp/ip port number and then re-enable VMRC.
If it does not work consider rebooting your host, if possbile.
Regards,
Niels
Woodrow
Hi there, was having the same problem and switching to use Port 6000 enabled me to connect to the VS.
Jesse
open a command prompt and run netstat -ano
my guess is that you will see ip address 0.0.0.0:5900 listed. that is why you cannot connect on 5900. Unfortunately I am still looking to find out why windows has locked this down. I discovered this on my streaming media server. it had locked port 80 down. ip address 0.0.0.0:80 and would not let me assign it to any other services. To fix it, the registry needed to edited. hkeyLM, system, currentcontrolset, services, http, parameters. I had to add a multi-string value called ListenOnlyList and use the servers ip address as the data.
Bryan
Was running into a very similar situation and it ended up being an authentication issue. Start>Run>inetmgr. Expanded the Web Sites folder. Right clicked on the Virtual Server and went to properties. Clicked on the Directory Security Tab. Clicked on Edit under Authentication and access control. I clicked on Enable anonymous access and put in the credentials of my Enterprise admin account and it worked fine. Hope this might work for you.
ErickL
(at least the 2950) with a DRAC, the DRAC is configured to use port 5900. I
actually had the reverse issue. VMRC worked for me but I could not get to my
DRAC card. moving the ports resulted in everything working.
Reperion GPS
Found the solution for my case :
If you have a Supermicro motherboard or system, and you have the PC doctor utiltity , it will install the WinVNC service on port 5900
Disable the service and your fine, any VNC will kill port 5900 for you