Static IP address changing to DHCP

Hello,

I have configures a Hyper-V Server 1212 host with a static IP address.  When I connect to the host and try to create a Virtual Switch so that I can connect as I add a VM, the creation fails and the Host's IP address is changed from Static to DHCP.  Did I miss something in the setup?

Thanks
HeilandSAsked:
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.

Muhammad BurhanManager I.T.Commented:
When virtual switch created, the physical LAN adapter is not configurable cause it just act like a hardware trough which the virtual switch connects.
For Example: if you named your physical LAN connection as Ethernet, after creating a vSwitch an another LAN adapter add-up with the name vEthernet. now you are supposed to configure that vEthernet instead of Ethernet(physical).
0
kevinhsiehCommented:
If you are creating a new virtual switch and attaching the physical NIC that is currently in use by the host, this can be expected. When you create a virtual switch, the NIC gets assigned to the virtual switch and then the host gets a new virtual NIC that is attached to the virtual switch. Since the host now has a NEW virtual NIC, the original NIC settings do not apply.

I like to configure the networking from the host itself, so things like the network getting reconfigured don't break the management connection between my workstation and the host. I use powershell. These commands get a list of all of the network adapters, creates a switch independent NIC team, and then creates a virtual switch connected to that NIC team.

# see which adapters the server currently has, and their status
get-netadapter
# create a new NIC team
new-netlbfoteam -name TEAM-TRUNK -teammembers "ethernet 2","ethernet 4","ethernet 5",ethernet 6"
# create a new external virtual switch and assign the NIC team to it
new-vmswitch -name ExternalSwitch -allowmanagementos 1 -netadaptername TEAM-TRUNK

Open in new window

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
HeilandSAuthor Commented:
Thanks for your help.  This resolved the issue.
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.