Hyper-V - 2 guests need to be able to communicate with each other only.

I'm under a very tight deadline here as I go on leave tomorrow for 3 weeks. I have a brand new physical server which is going to a customer for him to do some development.

As part of the setup, I need to get 2 of his existing Hyper-V guest running on this physical server so that they work as they would in the production environment, but I this instance can only communicate with each other.

One of these is a domain controller, the other is a SharePoint server.

I can only seem to get these to show as "Unidentified network" and subsequently won't communicate with each other.

I've tried setting the network to the NIC of the host (and setting the VLAN on both guests as 987), I've also tried connecting both to an Internal switch and a Private switch. In all instances with the same result of unidentified network.

The DC has a static IP, and the SharePoint server should be getting it's IP from DHCP of the DC.

I would be very grateful for some help!
LVL 17
Chris MillardAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
use a private switch and on each vm set the static ip addresses
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Eric_PriceCommented:
As David said you'll need to create a "private" switch. Without an actual router and default gateway set in the guest I'm not entirely sure it will ever say anything but "unidentified network". If one of them is a DC though and you point the SP server to it your name resolution and everything should work. You should be able to ping each other from the respective VMs. If you cant, turn off the firewall with netsh advfirewall set allprofiles state off at the command prompt and try again. If that STILL doesn't work you'll need to review your network settings.

I'm curious. If these two guests only talk to each other, how will the developer interact with them? Its easy of course to add another guest for a client, but unless hes working directly on the box, there will be no way to remote into it if you're using a private network switch.
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
If these two guests only talk to each other, how will the developer interact with them? Its easy of course to add another guest for a client, but unless hes working directly on the box, there will be no way to remote into it if you're using a private network switch.

He doesn't have to work directly on the box.  He can use RDP or the Hyper-V Manager to remotely connect to the host and then open console Windows.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Chris MillardAuthor Commented:
The customer will have physical access to the server in his office.
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
We would set up a Private network called "vSwitch - Dev"

We would then set up the VMs and attach their vNICs to that vSwitch.

Static IPs would be assigned to both.

A third VM would be installed with Windows Server 2008 R2 and RRAS set up to provide NAT outbound (x.x.x.1 IP) and we would publish HTTPS, HTTP, and RDP inbound to the required VMs. We call this VM "Router".

For Dev purposes we could set up a DNS A record in our internal DNS for DevEnv.Domain.Local and point it to the "public" IP on the "Router".

This gives full access via RDP to one of the VMs as well as full "production" style access for the dev environment.

EDIT: Subnet for the VMs would not be the same as the production network.
0
Chris MillardAuthor Commented:
The network is showing as "Public" on the DC, and (I guess) for this reason, some of the domain related services are not starting. I cannot for example open ADUC.
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Set Network Location Awareness to Automatic (Delayed). This is SOP for us since the network stack sometimes is not initialized when this guy scopes out the network setup.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.

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.