Adding 2nd externall network results in "Cannot connect to RPC"
running: hyper-v server 2008 r2
condition: functional configuration on 30 virtuals. stable on year. 8 nic's on host 2 in use, 1 management access , other external virtual network virtuals' traffic.
trigger: (past) time add external virtual network distribute network traffic.
steps: connected network cable to a unused hyper-v server host nic. confirmed through hyper-v manager host recognized newly connected network cable , received address via dhcp. added new external virtual network through hyper-v manager. process drops hyper-v manager connectivity never came back.
i unable connect virtual host via hyper-v manager (cannot connect rpc service). logged onto host console , noted network settings still showed 3 virtual networks (the 2 original ones plus newly added one). diagnostic ran steps under "configure remote management" , following 2 original networks showing in network settings. still unable connect , manage using hyper-v manager.
please advise , in advance.
browsing...
hi,
according description, seems use created external virtual network bind network adapter using, hyper-v manager drops connectivity, expected behavior.
by way, can’t understand description “i logged onto host console , noted network settings still showed 3 virtual networks (the 2 original ones plus newly added one).” cleary. general speaking, after created second external virtual network, have 1 physical network adapter , 2 switches in network connection console.
in environment, created external virtual network bind management network adapter used, can connect hyper-v computer through new added network adapter ip address.
in addition, if still can’t work, may need destroy external virtual network , create again.
how can enable host access on nic within hyperv r2?
script: creating external-only virtual network hyper-v
script: creating external virtual network hyper-v
vincent hu
Windows Server > Hyper-V
Comments
Post a Comment