2nd NIC on Host - Setting Up for Remote Management

i'm little bummed....

i'm working on server 2k8 r2. have worked tail off install dc in vm guest. has worked splendidly, had fair share of research , got lot of forums. have 2 nics on intel server. after install ping (from client workstation)

1. nic 1 - virtual network x.x.x.10
2. new vm dc - x.x.x.11

and access needed (obviously actual nic 1 had single virtual network switch protocol). did have fix win32time issues, seemed all set.

then wanted set 2nd interface (nic 2) "remote management" ostensibly machine if hyper-v somehow disabled. plugged cable 2nd nic on server , switch, went ipv4 properties , tried enter new (unique) address 2nd interface. got message

"warning - multiple default gateways intended provide reundancy single network..." "they not function when gateways on 2 separate ... networks. want save configuration?"

i came here forums , did little research. found answer ben armstrong made sound warning , not worry, chose ok configure it. when went in check properties, though, had saved everything, default gateway--that blank. researched more...

the solution seemed needed go virtual network manager , turn off "allow management operating system share network adapter." did that. took bit of time. vm running @ moment, downed it. sometime during waiting (i can't remember if before or after unchecking) chose ok again warning multiple default gateways. , time took--i must've done right!

by time vm reached "off" status, "allow share" change had taken place. started vm up, , proceeded test connections via ping.

oooops! original x.x.x.10 couldn't return packets. looked in network connections, , see old virtual network adapter has been deleted , replaced--with virtual network 2 (it's like the sequel of bad movie). problem? well, adapter has correct ip settings original used have, it's saying "network cable [is] unplugged." , if try go properties , save out again (even though it's configured way), multiple default gateways warning again.

questions:

1. is there way "undo" did, or have lost killer, crisp original , have deal sequel?
2. what did wrong?
3. how fix it?

any appreciated. can tell information on setting 2nd nic remote management thin , dicey--not there , is, isn't altogether clear.

cheers!

---

noel stanford oveson
jeremynlso
cne, clse, mcse, mcts, mcitp
berlin, germany

hi jeremy possible undo it.  you'll have "accept" folly, isn't terrible since caught early.

1. shutdown vm
2. using hvm remove vswitch created nic1 pre-hyper-v state
3. blank out ip, gateway, dns, etc.  information not needed nic once convert vswitch.  if nic1 on dhcp enabled network, you'll have manually enter in bogus info.
3*. i've noticed on systems, depending upon network config, entering in bogus info results in none of vms being able talk proper network despite being on proper switch port , configuration.  if case, you'll have assign what's equivalent of "switch port ip" nic, leave gateway blank.
4. recreate vswitch nic1 , ensure allow management of os unchecked.
5. on nic2, assign ips including gateway management server, create vswitch allow management of os checked.  necessary if require 2 virtual networks, otherwise can use dedicated.
6. on vm, point vm nic newly recreated virtual network.
7. if did not remove nic vm properties , re-add, should in theory hold same ip information , should work, if detects new nic or doesn't work, re-apply ip settings , test.

Windows Server  >  Hyper-V