Hyper-V Gen 2 Windows Server 2012 R2 VM cannot define static IP address

Question

Hi,
I have setup a physical server with Windows Server 2012 R2. It has only the Hyper-V role installed. The physical server has two NICs that I have teamed with Hyper-V port as the load balancer. I have created 1 VM on this Hyper-V server that is a
Generation 2 VM running Windows Server 2012 R2. It has one NIC in the guest OS that is connected to the Hyper-V switch.
Now the Guest OS works fine and network connectivity is great when using DHCP but when I configure a static IP address in the Guest OS all network connectivity is lost even with correct IP configuration. Is this something to do with a Gen 2 VM?
A little more background - We have another Hyper-V server running Windows Server 2012 R2 with the same NIC teaming in the Host OS, on this Hyper-V there is a GEN 1 Windows Server 2012 R2 that has a static IP configured which is working normally.
Any help is appreciated.

Answer 1

I have resolved the issue. It appeared the hard IP phones were using the same IP range that I was attempting to use so of course the VM could not use the IP Address. Silly mistake.
Elliot, I suggest you mark as Helpful and Answer any responses above that were helpful to you in getting this issue resolved. This is how the forums work.
For example, if a response mentioned "VM generation has no effect on the vNIC." and that pointed you in the direction of troubleshooting networking instead of wasting your time looking into VM generations, that may be considered "Helpful"
If a response mentioned "Make sure you're using valid IPv4 settings" and indeed you ended up having invalid IP settings such as a duplicate IP, this may be considered "Answer"
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx