Windows Server TechCenter >
Windows Server Forums
>
Hyper-V
>
Hyper-V Manager suddenly unable to 'connect' to VM's
Hyper-V Manager suddenly unable to 'connect' to VM's
- Is anyone else having problems when running Hyper-v Manager remotely and suddenly being unable to connect to machines?
I'm using Hyper-v as a host for test environments. The 2008+Hyper-v server sits in the server room, and I access it primarily from my desktop system that runs Vista Business. The server has two NIC's, and one is dedicated to the virtual switch, and the other hooks just to the HOST partition.
I mostly access the VM's via the 'console' emulation provided by using Hyper-V Manager's "Connect" function. (I sometimes remote-desktop to the VM's but in most cases I find using 'Connect' works better for what I am doing.) and I'm also using Hyper-V Manager to manage snapshots and reverting to specific snap-shots on specific VM's
I'm making heavy use of snapshotting (and loving it) and frequently switching between VM's and also flipping between snap-shotted states depending on what I need for the tests I'm running.. In this respect Hyper-V is a QA Professional's dream environment. Words cannot express how much I am loving this, especially when I need to test setup applications!
The only real problem I'm having is that at times the 'connect' function will just flat out stop working. Even closing and re-opening HVM doesn't get it going. Strangely enough when this happens I can still connect using the nifty Hyper-V Monitor vista Gaget running in my sidebar. I've not tried to start tracking, so I'm not sure if there is a pattern to how many times I can use 'connect' before it stops working. ALso it seems that a little bit later it will start working again.. Or I'll get a connection error message indicating I need to flush my systems DNS cache, and after doing that things start working again.
I'm sure a pattern will emerge but at present I'm stumped as to what is causing this, and what I can do to 'fix' it when it happens.
--Chuck
Answers
- Hello,
Do you mean the Hyper-V Manager console on the Windows Vista machine?
This sounds like the same issue that MarkEmery encountered. Please see the following post:
He gave some explanation on this problem. The workaround, for now, is either to set the DCOM permission to "anonymous" on the Windows Vista machine (by following the steps in John Howard's blog), or to use static IP address for that Windows Vista machine so that the DNS name can be resolved immediately.
Please try this to see if the problem remains.
Best regards,
Chang Yin
- Marked As Answer byMike Sterling [MSFT]MSFT, OwnerTuesday, June 02, 2009 9:54 PM
All Replies
- Hello,
Do you mean the Hyper-V Manager console on the Windows Vista machine?
This sounds like the same issue that MarkEmery encountered. Please see the following post:
He gave some explanation on this problem. The workaround, for now, is either to set the DCOM permission to "anonymous" on the Windows Vista machine (by following the steps in John Howard's blog), or to use static IP address for that Windows Vista machine so that the DNS name can be resolved immediately.
Please try this to see if the problem remains.
Best regards,
Chang Yin
- Marked As Answer byMike Sterling [MSFT]MSFT, OwnerTuesday, June 02, 2009 9:54 PM
- Hmmm I'll have a look into that. The issue does seem similar, but also is different. This is different from his because most times I don't get any kind of error message, it just goes from having been working, to 'nothing happens with no error message' when I try to connect to the vm.
His issue seemed to be with HVM in the first place, and mine is in using the HVM functions for connecting to the VM's console session. SO in my case HVM has launched, and connected to the Hyper-v server, and all is working well, and the failure happens when I try to use the 'connect' function. ALSO when the problem happens I can usually still connect to the VM using the Vista 'Hyper-v Monitor' sidebar Gaget. So the problem seems to be with Hyper-V Manager not being able to connect me to the VM, NOT with the actual process of my system connecting to the VM (since it works from the gaget)
Setting any kind of anonymous access permissions is not a desirable solution, especially when all the systems are members of a domain already, and should be able to create fully authenticated connections.
Giving my workstation a fixed IP is also really not an acceptable solution, the IT folks want to use fixed ip's only for server resources.
(besides my system has a long IP lease, and is always on, so its IP effectively never changes, so the DNS should never need updating no?)
--Chuck- Edited byChuck vdL Tuesday, September 02, 2008 4:29 PMadded bit of additional info re symptoms
- I had a similar issue from a Windows 7 client. Opening the MMC using the "Run as Administrator" allowed me to connect to the VM in the Hyper-V Manager.
- I had a similar issue as well - clicking 'connect' does absolutely nothing. Runing "c:\Program Files\Hyper-V\vmconnect.exe" directly shows the initial UI, but when I click "connect" it just hangs.
It turns out that 64-bit .NET applications were accidentialy disabled on my machine (and the VM connect tool doesn't support running in the WOW). Running "c:\windows\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe set64" fixed the problem.
I hope this is helpful to others.
Rick Byers - Microsoft Common Language Runtime team
