Guest Noah Wang Posted March 27, 2008 Posted March 27, 2008 My Hyper-V Guests cannot traverse through NAT to gain internet access. I followed the guide by John Paul Cook linked here http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx Here are the steps I took. 1. Install Windows 2008 Server 2. Setup static IP on physical network card 3. Deploy Hyper-V roles 4. In Virtual Network Manager created an internal only network 5. Define the newly created internal network with IP: 192.168.1.1 Subnet 255.255.255.0 6. Deploy RRAS 7. Configure NAT 8. Pointed public interface to the physical network card 9. Pointed internet network to the internal network 10.Disable firewall on host in relation to the internal network Guest OS receives DHCP from the RRAS Guest OS is able to ping 192.168.1.1. Guest OS is able to resolve internet DNS name. Guest OS cannot traverse through NAT to the internet. My primary goal is to enable Guest OS(s) ability to reach the internet. But I have no idea what’s wrong with my configurations.
Guest Bill Grant Posted March 27, 2008 Posted March 27, 2008 Re: Hyper-V, RAAS woes. . . Please help That setup works fine for me. You should not need to disable the firewall on the host. Can you ping the host's static public IP from the guest? Does it work if you let the public NIC of the host get it IP address automatically? "Noah Wang" <Noah Wang@discussions.microsoft.com> wrote in message news:E412F270-7172-4996-BDC9-D67FD74A69A9@microsoft.com... > My Hyper-V Guests cannot traverse through NAT to gain internet access. > I followed the guide by John Paul Cook linked here > http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx > > Here are the steps I took. > 1. Install Windows 2008 Server > 2. Setup static IP on physical network card > 3. Deploy Hyper-V roles > 4. In Virtual Network Manager created an internal only network > 5. Define the newly created internal network with > IP: 192.168.1.1 > Subnet 255.255.255.0 > 6. Deploy RRAS > 7. Configure NAT > 8. Pointed public interface to the physical network card > 9. Pointed internet network to the internal network > 10.Disable firewall on host in relation to the internal network > > Guest OS receives DHCP from the RRAS > Guest OS is able to ping 192.168.1.1. > Guest OS is able to resolve internet DNS name. > Guest OS cannot traverse through NAT to the internet. > > My primary goal is to enable Guest OS(s) ability to reach the internet. > But I have no idea what’s wrong with my configurations. >
Guest Noah Wang Posted March 27, 2008 Posted March 27, 2008 Re: Hyper-V, RAAS woes. . . Please help From the guest I am able to ping the host static Public IP. Static IP is required as I have a static IP. From the host I am able to ping http://www.news.com. From the guest I get request time out when pinging http://www.news.com "Bill Grant" wrote: > That setup works fine for me. You should not need to disable the firewall > on the host. > > Can you ping the host's static public IP from the guest? Does it work if > you let the public NIC of the host get it IP address automatically? > > "Noah Wang" <Noah Wang@discussions.microsoft.com> wrote in message > news:E412F270-7172-4996-BDC9-D67FD74A69A9@microsoft.com... > > My Hyper-V Guests cannot traverse through NAT to gain internet access. > > I followed the guide by John Paul Cook linked here > > http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx > > > > Here are the steps I took. > > 1. Install Windows 2008 Server > > 2. Setup static IP on physical network card > > 3. Deploy Hyper-V roles > > 4. In Virtual Network Manager created an internal only network > > 5. Define the newly created internal network with > > IP: 192.168.1.1 > > Subnet 255.255.255.0 > > 6. Deploy RRAS > > 7. Configure NAT > > 8. Pointed public interface to the physical network card > > 9. Pointed internet network to the internal network > > 10.Disable firewall on host in relation to the internal network > > > > Guest OS receives DHCP from the RRAS > > Guest OS is able to ping 192.168.1.1. > > Guest OS is able to resolve internet DNS name. > > Guest OS cannot traverse through NAT to the internet. > > > > My primary goal is to enable Guest OS(s) ability to reach the internet. > > But I have no idea what’s wrong with my configurations. > > > >
Guest Bill Grant Posted March 27, 2008 Posted March 27, 2008 Re: Hyper-V, RAAS woes. . . Please help My guess is that it is a problem with a device driver. On the host, check the NIC driver. Disable TCP offload if it is enabled. "Noah Wang" <NoahWang@discussions.microsoft.com> wrote in message news:34C5E491-CC2A-4F05-97D8-BD9B27286282@microsoft.com... > From the guest I am able to ping the host static Public IP. > Static IP is required as I have a static IP. > > From the host I am able to ping http://www.news.com. > From the guest I get request time out when pinging http://www.news.com > > "Bill Grant" wrote: > >> That setup works fine for me. You should not need to disable the >> firewall >> on the host. >> >> Can you ping the host's static public IP from the guest? Does it work >> if >> you let the public NIC of the host get it IP address automatically? >> >> "Noah Wang" <Noah Wang@discussions.microsoft.com> wrote in message >> news:E412F270-7172-4996-BDC9-D67FD74A69A9@microsoft.com... >> > My Hyper-V Guests cannot traverse through NAT to gain internet access. >> > I followed the guide by John Paul Cook linked here >> > http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx >> > >> > Here are the steps I took. >> > 1. Install Windows 2008 Server >> > 2. Setup static IP on physical network card >> > 3. Deploy Hyper-V roles >> > 4. In Virtual Network Manager created an internal only network >> > 5. Define the newly created internal network with >> > IP: 192.168.1.1 >> > Subnet 255.255.255.0 >> > 6. Deploy RRAS >> > 7. Configure NAT >> > 8. Pointed public interface to the physical network card >> > 9. Pointed internet network to the internal network >> > 10.Disable firewall on host in relation to the internal network >> > >> > Guest OS receives DHCP from the RRAS >> > Guest OS is able to ping 192.168.1.1. >> > Guest OS is able to resolve internet DNS name. >> > Guest OS cannot traverse through NAT to the internet. >> > >> > My primary goal is to enable Guest OS(s) ability to reach the internet. >> > But I have no idea what’s wrong with my configurations. >> > >> >>
Guest Noah Wang Posted March 28, 2008 Posted March 28, 2008 Re: Hyper-V, RAAS woes. . . Please help I tried your suggestion still stuck. Here is the network card properties: Should I try another ethernet card? Is there one that is recommanded? Intel® 8256V 10/100 Network Card Adaptive inter-Frame Space Disabled Flow Control Disabled Interupt Moderation Enabled Interup moderation rate Adaptive IPv4Chesum Offload Disabled Jumbo Packt Disable Large send offload v2 (IPv4) Disabled Large send offload v2 (IPv6) Disabled Link Speed & duples Auto Negotiation Local Administered Address Not Present Log Link State Event Enabled Priort & VLAN Enabled Recieve Buffers 256 Recieve side Scaling Disabled TCP Checksum Offload (IPv4) Disabled TCP Checksum Offload (IPv6) Disabled Transmit Buffers 512 UDP Checksum Offload (IPv4) Disabled UDP Checksum Offload (IPv6) Disabled Wait for Link Auto Detect Other VM network card IP Checksum Offload (IPv6) Disabled Network Address Not Present TCP Checksum Offload (IPv4) Disabled TCP Large Send Offload (IPv4) Disabled "Bill Grant" wrote: > My guess is that it is a problem with a device driver. On the host, check > the NIC driver. Disable TCP offload if it is enabled. > > "Noah Wang" <NoahWang@discussions.microsoft.com> wrote in message > news:34C5E491-CC2A-4F05-97D8-BD9B27286282@microsoft.com... > > From the guest I am able to ping the host static Public IP. > > Static IP is required as I have a static IP. > > > > From the host I am able to ping http://www.news.com. > > From the guest I get request time out when pinging http://www.news.com > > > > "Bill Grant" wrote: > > > >> That setup works fine for me. You should not need to disable the > >> firewall > >> on the host. > >> > >> Can you ping the host's static public IP from the guest? Does it work > >> if > >> you let the public NIC of the host get it IP address automatically? > >> > >> "Noah Wang" <Noah Wang@discussions.microsoft.com> wrote in message > >> news:E412F270-7172-4996-BDC9-D67FD74A69A9@microsoft.com... > >> > My Hyper-V Guests cannot traverse through NAT to gain internet access. > >> > I followed the guide by John Paul Cook linked here > >> > http://sqlblog.com/blogs/john_paul_cook/archive/2008/03/23/using-wireless-with-hyper-v.aspx > >> > > >> > Here are the steps I took. > >> > 1. Install Windows 2008 Server > >> > 2. Setup static IP on physical network card > >> > 3. Deploy Hyper-V roles > >> > 4. In Virtual Network Manager created an internal only network > >> > 5. Define the newly created internal network with > >> > IP: 192.168.1.1 > >> > Subnet 255.255.255.0 > >> > 6. Deploy RRAS > >> > 7. Configure NAT > >> > 8. Pointed public interface to the physical network card > >> > 9. Pointed internet network to the internal network > >> > 10.Disable firewall on host in relation to the internal network > >> > > >> > Guest OS receives DHCP from the RRAS > >> > Guest OS is able to ping 192.168.1.1. > >> > Guest OS is able to resolve internet DNS name. > >> > Guest OS cannot traverse through NAT to the internet. > >> > > >> > My primary goal is to enable Guest OS(s) ability to reach the internet. > >> > But I have no idea what’s wrong with my configurations. > >> > > >> > >> > >
Recommended Posts