Windows Server TechCenter >
Windows Server Forums
>
Hyper-V
>
Error "Cannot connect to RPC service on Computer ..." after creating the first External Virtual Network
Error "Cannot connect to RPC service on Computer ..." after creating the first External Virtual Network
Firstly Id like to thank the folks who regularly post solutions in this forums section. I have found everyone input to be invaluable in learning the ropes of Server 2008 R2 Core, Hyper-V and RSAT.
My issue is this:
Upon the creation of a External Virtual Network on my newly configured Hyper-V host (with 1 virtual machine) by following the steps detailed here http://technet.microsoft.com/en-us/library/ee247420%28WS.10%29.aspx ...
I find myself unable to reconnect to the Hyper-V host with the error "Cannot connect to RPC service on computer (its IP). Make sure you RPC service is running" when I start Hyper-V Manager.
Referring to documentation I have read, it is common to loose connection to the host during the process if the IP settings are static and one wont be able to reconnect until the IP settings are re-entered.
Quote: "You should be aware that external network connectivity will be temporarily disrupted when an external virtual network is created or deleted."
http://technet.microsoft.com/en-us/library/cc816585%28WS.10%29.aspx
Yes I did loose connection as the settings were being applied. I cannot confirm that they did take effect though I am unable to connect back in (hence the reason foe this post :).
To move forward I did sign back into the console and set the static IP settings to the NIC that I had attached the Virtual Network to, as well as restarted the RPC service for good measure. Result was the same error as noted above.
Sidebar: The server I'm running does have two physical NIC's I am able to RDP back into the box on the 2nd NIC/IP Address, but unable to Connect Hyper-V to it as well.
I can give more info to clear up any fuzzy points, but I think the info I have detailed now is a good start for anyone willing to lend a hand.
Thanks and cheers
- Edited byCobaltCND Tuesday, September 01, 2009 8:31 PMspelling
Answers
- I believe that Windows On Windows is a shell component and therefore not available on a Core installation.
However, I see that a quick search has proved me wrong (at least partly).
It appears that the folowing components have WOW modules for support of 32-bit applicaitons:
http://blogs.technet.com/server_core/archive/2009/05/05/wow64-support-on-server-core-in-windows-server-2008-r2.aspx
By "backup and remove" I mean go backward in your steps. And remove all of the Virtual Networks.
You would have to target it against the one interface that you do have, or run a script at the console (you could use a USB device).
And, unfortunately the Hyper-V management console or SCVMM is required to do that.
It is possible to do it by WMI but I do not know the commands off the top of my head.
Also, if you are willing to be friendly with PowerShell - there is a set of PowerShell cmdlets on CodePlex that you can use
http://www.codeplex.com/PSHyperv
I beleive that you had one interface available to get to the host right? Any interface to the parent parition can serve as a management interface.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byVincent HuMSFT, ModeratorMonday, September 07, 2009 3:02 AM
All Replies
- You mention: " did sign back into the console and set the static IP settings to the NIC that I had attached the Virtual Network to"
When you created an External Virtual Network and attached it to a Physical NIC - that Physical NIC can no longer have an IP address assigned directly to it.
Your host should have had an additional Virtual Network Adapter appear in the list of Network Adapters. It is this new interface that would need your manually set IP address.
Your origional physical NIC should now only have one binding - it should be bound to the Virtual Network Switch Protocol - no other bindings should be enabled.
If you have Hyper-V R2 - there is an option to allow the host to communicate on this virtual network - this will add the virtual nic described above. If this option is not selected, the host will not be able to communicate on this External Virtual Network.
In most cases it is easire to back up at this point and remove the External Virtual Network, observe the Network Connections, create a new External Virutal Network, observer the Network Connections again - and not the new one that you now need to change.
All that being typed....
Also be sure the update to the latest Hyper-V patch if you are not using Hyper-V R2.
There is a bug in this area that does not pull manual IP settings forward properly when an External Virtual Network is created - this bug has been fixed.
Be sure to install the Server 2008 Service Pack if you are not running R2 before attempting to create a new External Virtual Network.
Brian Ehlert (hopefully you have found this useful) - Thanks Brian for your quick reply. Yes the NIC I assigned the Virtual Network to now shows up as the name I gave the virtual network upon setup.
You write "In most cases is easier to backup and remove the External Virtual Network" Can you give me more information?
I could understand doing it via Hyper-V Manager, but this issue prevents me from getting to the Virtual Network Manager.
Seeing as I'm running a Core build and life on a Windows command line is new to me, I was looking at using the Smart-X app to manage my Core Server. I understand it requires WOW64 (as smart-x is a 32 bit app). I ran the "oclist" command and I do not see that I have WOW64 installed (its actually not on the list altogether). Is WOW64 something I can download and install, does someone have a link to it perhaps?
Also I am currently downloading Hyper-V Manager R2 as well!
thanks in advance! - I believe that Windows On Windows is a shell component and therefore not available on a Core installation.
However, I see that a quick search has proved me wrong (at least partly).
It appears that the folowing components have WOW modules for support of 32-bit applicaitons:
http://blogs.technet.com/server_core/archive/2009/05/05/wow64-support-on-server-core-in-windows-server-2008-r2.aspx
By "backup and remove" I mean go backward in your steps. And remove all of the Virtual Networks.
You would have to target it against the one interface that you do have, or run a script at the console (you could use a USB device).
And, unfortunately the Hyper-V management console or SCVMM is required to do that.
It is possible to do it by WMI but I do not know the commands off the top of my head.
Also, if you are willing to be friendly with PowerShell - there is a set of PowerShell cmdlets on CodePlex that you can use
http://www.codeplex.com/PSHyperv
I beleive that you had one interface available to get to the host right? Any interface to the parent parition can serve as a management interface.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byVincent HuMSFT, ModeratorMonday, September 07, 2009 3:02 AM
