Microsoft Hyper V Server - Remote admin

Hi

I have installed Hyper V server on a new server, i want to virtualise sbs 2008 premium i want to use the hyer v server (server core version) for the performance benifits i have downloaded my free copy and installed the server assigned it a name and static ip i have also give my vista sp1 laptop a static ip and i can connect via rdp but when i try manage the hyper v server via hyper v manager on my laptop i get rpc errors, i have a good idea that this is related to dns and firewall issues but if im setting up a new site first off and i have no dns server all i have is a sonicwall firewall a physical server with hyper v and my laptop to manage what should i use as a dns server till i have my sbs box up and running? microsoft need to make this easier to manage and quickly i have used this in my domain and it works http://blogs.technet.com/jhoward/archive/2008/04/01/part-4-domain-joined-environment-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx in a domain environment that has a dns server so i guess im asking whats the easiest way to setup and administer a new sbs premium site using your work domain joined laptop and a sonicwall firewall and switch?

again i can get it working in my work domain environment but not when i try setup a site from scratch.

thank you
nostrasystemsAsked:
Who is Participating?
 
nostrasystemsAuthor Commented:
u cant ping a hyper v install straight off the firewall blocks it, i sorted it by adding an a host record to the hyper v server and my laptop now it works perfect
0
 
dfxdeimosCommented:
So the Hyper-V server is NOT a member of a domain but your laptop IS?

What is the exact RPC error that you get when you try to connect with the Hyper-V manager?
0
 
nostrasystemsAuthor Commented:
Laptop part of my work domain  -   static address 192.168.16.100
Server with hyper v server installed part of default workgroup - 192.168.16.1
Then i have a router - 192.168.16.254

i dont have a dns server on this setup and i think this is whats causing the problems only isps dns configured in the router, i get the rpc service is unavailable in hyper v manager

any ideas whats the best practice when setting this up as a fresh install in a new site?

i have got this working in our office when it has been on our domain with an internal dns server

cheers
0
 
dfxdeimosCommented:
RPC error generally indicate that the server you are trying to remotely administer has something wrong with it. What is the exact error (in quotes) that you get when you try to connect to the Hyper-V server with the Hyper-V manager?

Can you ping the Hyper-V server? If so, post the results here.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.