"RPC Server is unavailable" error when remotely managing Hyper-V Server 2008.

Oops ...
:)

Philip

hi,

confirm if you are using vista to manage the hyper-v box you have applied the latest update for managing hyper-v from vista running on x64 with sp1

http://www.microsoft.com/downloads/details.aspx?familyid=88208468-0AD6-47DE-8580-085CBA42C0C2&displaylang=en

if this is windows 2008 box from which you are connecting to the hyper-v server then ensure that all the latest update are applied on the windows 2008 box as when you try to manage a hyper-v machine from windows 2008 you get errors with xml and rpc errors


bhanu

Hi bhanukir7
It's Vista SP1 with the Hyper-V component downloaded last Sunday from Microsoft, so assume the latest.

Hi MPECSInc:
I'm about to read through the links you posted - thanks. I did try stopping the firewall on both machines to see if that was a causal factor, but since read that if the firewall was only stopped it would still block ports? Can you coroborate?

if the firewall is stopped on both sides no ports will be blocked. Also check if there are any hardware firewalls and turn them off.

additionally check if the remote  procedure call(rpc) & remote procedure call(rpc) locater service are running on the Vista box and the windows 2008 box.

bhanu

HI bhanukir7
Yes, that's what I thought - the comment I read was that if the firewall was only stopped and not completely disabled then the ports might still be blocked. I've blitzed the server machine and started the build again - will take in both your and MPECSInc's comments during config and post back tomorrow.
Thx

After two more attempts with the HVRemote scripts published in John Howard's blog I managed to get the Hyper Server working. I think there's some good advise attached to the links published by MPECSInc:so points to him.

Cheers

Thanks for that!
Philip

just for information purposes only:

we struggled a few hours about conenction to hyper-v-free-server via microsoft-vpn. the solution (beyond several guides as you already know) that the add the entry of hostname (within workgroup) and ip in our local hosts-file!

have fun!

regards

Thanks a lot... pit1140! All the solutions above are of course valid and important but we have run into the same problem - all is set, all is allowed on firewall, every console (EventViewer, Services, Wndows Firewall etc.) can be operated remotely... except Hyper-V and Disk Management. Even with the firewalls down on both sides it just does not work so we figure that much that it can't be blocking problem. The solution was to add machine names to hosts files as mentioned above. We did it at the beginning but we did it only on client but not the server (we have been configuring several servers at once and just missed the entry on one, therefore just this one had problems). Therefore without this critical post above we would be still wandering in the dark... 39!

great! have fun! ;)