Virtual Machine No Communication


1) Have a 2016 OS running hyperv manager, the Windows 2016 OS has no configurations are on it. It is not a DC for example. Not yet anyway.
2) Have added a virtual Windows 2008 R2 server taken from an actual real physical server into hyperv manager within 2016 OS.
3) Have setup the 2016 OS with a static ip that is in the same scope as the 2008R2 server's static ip address.
4) At this stage neither will talk to each other i.e. ping, this is because the 2008R2 server isn't seeing the virtual network adapter of the 2016 OS.

I've not used hyperv manager where i've added a virtual server from an actual physical server before. Normally, if creating a new virtual server on an OS it doesn't pose a problem. What is the way around this please for them to talk to each other?
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.

Paul MacDonaldDirector, Information SystemsCommented:
Does the VM have a network adapter assigned to it in Hyper-V Manager?  Look at the Settings for the VM and see.
discoveranotherAuthor Commented:
Hi Paul, yes the 2008R2 VM has a virtual adapter already assigned to it. Looks like this adapter is  the actual network adapter of the windows 2008R2 machine.

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
discoveranotherAuthor Commented:
Exact answer
Paul MacDonaldDirector, Information SystemsCommented:
Can you please expound on what the solution was?  It may help someone in the future.
discoveranotherAuthor Commented:
The virtual machine 2008R2 did have an existing network adapter attached to it. I removed this and added the network adapter from the 2016 OS and it sorted the issue, assigning the original static ip address to the adapter.
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

From novice to tech pro — start learning today.