Új hozzászólás Aktív témák

• #2115 DopeBob addikt iwu #2114

  Új Válasz 2011-08-02 22:21:42 #2115

  Új hozzászólás

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  Privát üzenet küldése

  

  DopeBob

  addikt

  válasz iwu #2114 üzenetére

  Short Answer:
  Buy another NIC and dedicate it to your Hyper-V tasks.
  Long Answer:
  Install a second physical NIC on your Hyper-V server and patch it into your network.
  Open the Virtual Network Manager in the Hyper-V console and remove all virtual networks
  Configure your secondary NIC with an available IP from you LAN and a subnet mask. Leave the gateway, DNS and WINS empty.
  Open the Virtual Network Manager in the Hyper-V console and create a virtual network using the secondary NIC.
  Open Add/Remove Bindings on the DHCP server and remove the checks from all bindings except for your NIC. You may get an ambiguous error about an incorrect parameter which you can ignore.
  Restart the DHCP server and open Add/Remove Bindings to verify that the changes you made were saved.
  If all went well you should now be able to get DHCP leases from the Hyper-V server’s server primary NIC and use the secondary NIC for Virtual Machine access.
  *If you use the Windows firewall, disable it for this process and re-enable it when DHCP works with the Virtual NIC.
  This worked for me and I hope it helps to get things working for you. - Jaxplanet

  Ez google, úgyhogy nem tudom, hogy jó megoldás e esetleg ezzel lehet próbálkozni még.

  MZ/X

Új hozzászólás Aktív témák