External networking in Virtual Machine
Server 2008 R2 Standard is the host.
Server 2003 R2 sp2 Standard is the guest.
Machine is Proliant ML370 G6. Which has a 4 port GB NIC. Only two ports are connected.
Hyper-V is installed first then the virtual network using one NIC port is created.
Virtual machine was created and 2003 R2 installed.
Hyper-V Integration services installed in guest OS after OS installed.
HP network configuration utility installed/uninstalled (allows teaming of NICs).
HOST Network Connections:
Physical network adapter only has the "Virtual Network Switch Protocol' selected.
The 'Connection' created by Hyper-V has all selected except 'Virtual Network Switch Protocol' and IPV6 selected.
The 'Connection' TCP/IP properties has both of our DNS servers listed and does not have a static IP.
GUEST Network Connections:
Only connection listed has a static IP address and our DNS and WINS servers listed correctly.
Problem:
Guest OS is unable to browse the network. IE8 is unable to browse the internet and unable to browse our intranet. Windows Explorer is unable to browse our network.
Host is able to browse internet and intranet.
Troubleshooting attempts:
When I ping -a [LAN IP] the host name is successfully returned.
WHen I ping -a [host name] the IP Address is successfully returned.
When I ping -a [internet ip address] the host name is successfully returned.
WHen I ping -a [web address] the IP Address is successfully returned however 'Request timed out' sometimes occurs.
Status bar in IE displays correct IP address for the website.
Re-install of Hyper-V and guest OS.
Changed which physical NIC the virtual switch is connected to.
static ip on host virtual connection.
removed DNS listings in virtual conncection.
re-install host integration services.
using different ports on the quad port nic.
removing the gateway on the virtual connection in host.
using netmask 255.255.0.0
We have a HP DL180 G5 with Hyper-V installed with two NIC ports. I have examined both Host and Guest OS network connection configurations and tried to make them match.
The only difference, besides the hardware, I see is that the server with the problem guest has a host OS version R2. Both guest OSs are R2.
I have spent at least a couple of hours reading blog posts and technet articles without resolution. Most do not deal with troubleshooting connection problems.
Any suggestions would be appreciated.
Thanks.
Answers
Hi,
Base on your Troubleshooting attempts, it seems the ping works properly.
Please perform the following suggestions to test whether it works.
1. If you have teaming, please remove it(Microsoft doesn’t support teaming officially, you have to contact the manufacture of the device)
2. Please disable TCP offloading.
If the issue continues, please following these steps:
1. Remove Hyper-V Virtual Networking.
2. Remove Hyper-V role and enable it after the restart.
3. Try to access your LAN resource and the internet from this computer to test whether it works. If works, go to next step.
4. Disable two physical NICs(You mentioned only two ports are connected)
5. Leave two NICs get IP address from DHCP server
6. Ty to access your LAN resource and the internet from Hyper-V host computer to test whether it works. If works, go to next step.
7. I Hyper-V Manager console, create a new External Virtual Networking bind to one physical NIC, disable the virtual network adapter created by system.(leave the host communication through another physical NIC)
8. Ty to access your LAN resource and the internet from Hyper-V host computer to test whether it works.
9. Connect a VM to the External Virtual Network and test whether you can access the LAN resource and the internet.
Vincent Hu
- Marked As Answer byMethum Monday, October 05, 2009 1:14 PM
All Replies
Hi,
Base on your Troubleshooting attempts, it seems the ping works properly.
Please perform the following suggestions to test whether it works.
1. If you have teaming, please remove it(Microsoft doesn’t support teaming officially, you have to contact the manufacture of the device)
2. Please disable TCP offloading.
If the issue continues, please following these steps:
1. Remove Hyper-V Virtual Networking.
2. Remove Hyper-V role and enable it after the restart.
3. Try to access your LAN resource and the internet from this computer to test whether it works. If works, go to next step.
4. Disable two physical NICs(You mentioned only two ports are connected)
5. Leave two NICs get IP address from DHCP server
6. Ty to access your LAN resource and the internet from Hyper-V host computer to test whether it works. If works, go to next step.
7. I Hyper-V Manager console, create a new External Virtual Networking bind to one physical NIC, disable the virtual network adapter created by system.(leave the host communication through another physical NIC)
8. Ty to access your LAN resource and the internet from Hyper-V host computer to test whether it works.
9. Connect a VM to the External Virtual Network and test whether you can access the LAN resource and the internet.
Vincent Hu
- Marked As Answer byMethum Monday, October 05, 2009 1:14 PM
- Disabling TCP Offloading appears to have resolved this issue.
I was able to disable this network connection feature using the gui. I access the feature when I clicked on the properties submenu option when I right clicked on the adapter in the Network Connections window. I then clicked on the 'Configure' button for the adapter. Then I clicked on the 'Advanced' tab and the 'TCP Checksum Offload IPv4' Property was available and the Value disabled was also available. I also disabled the 'TCP Checksum Offload IPv6' Property as well.
I have a HP ML370G6 server with the Quad Port NC365i NIC.
I disabled this property for the physical adapter as well as the Microsoft Virtual Adapter on the host machine. The virtual machine adapter did not have this option available.
Thank you Vincent Hu.
