External virtual network acts like internal
- 1 physical nic (with fixed ip 192.168.125.x)
- latest nic driver (realtek) installed
- 1 external virtual network (created @ install time)
- can ping (connect) other physical machines in subnet 192.168.125.x
- 2 guest vms (w2k3 server)
- if guest vms have been set getting ip-address via dhcp, apipa address
- if guest vms have been set fixed ip-addresses (192.168.125.x), i'm able ping (connect) host or other guest not other physical machines in subnet
looks external virtual network acts internal!?
any ideas / solutions?
i’d suggest try following suggestions:
1, issue may occur when network adapter or driver incompatible hyper-v.
i understand have installed latest driver realtek nic. may check whether there other drivers available; if so, may test whether work. if windows server 2008 has build-in network driver nic, suggest use build-in driver see whether works. meanwhile, still suggest install model of network adapter on server see whether works. in way, can isolate whether incompatible network adapter issues. in past, have seen similar issues resolved replacing physical network adapter.
2, delete , recreate virtual network in vms , windows server 2008.
i understand have deleted virtual network , recreate it. i’d suggest performing following steps remove virtual network adapter in vm , virtual network in hyper-v server thoroughly test again.
1) shutdown 2 windows server 2003 vms if running , remove legacy network adapter or virtual network adapter in 2 windows server 2003 vms , then.
2) delete external virtual network binds realtek physical nic in host machine , restart windows server 2008.
3) in hyper-v manager, open virtual network manager, in new virtual network option, select “external” , click add, , choose connection type “external”, select realtek nic.
4) restart windows server 2008 host machine.
5) add virtual network adapter in windows server 2003 vms , configure attach newly created virtual network.
6) start virtual machine test issue again.
3. reported switches incompatible hyper-v. example, switches not accept 2 different mac addresses same switch port. cause problems. isolate switch/router issue, i’d suggest connecting host server , computer hub , test whether vms can ping other computer connects same hub. can set fixed ip 2 physical computer , 2 vms test.
4. have installed network monitor tools? these tools may interrupt normal network traffic. if possible, please uninstall these tools test whether helps.
best regards,
vincent hu
Windows Server > Hyper-V
Comments
Post a Comment