gaa18
asked on
Hyper-V VM's cannot access the internet.
hi all,
we have a setup consisting of:
1. physical instance of server 2008 SP3 R1 not part of a domain- running hyper-v with 5 Nics. 4 of them are in a balancing team which is assigned as an external network within hyper-v and the other one is the servers own NIC for remote admin.
2. Virtual instance of SBS2008 which is domain controller, exchange, DHCP, DNS server etc.
the issue is this... the SBS is unable to connect to the internet. i have no idea why but it can access and ping the internal network.. it says that it has internet connectivity but you cannot reach the internet or ping any external addresses. it did work on setup at the weekend but has dropped today.
why would this happen?
on the physical server in the network and sharing centre it states that the connection only has local connectivity so i assume the issue is there but why could this happen? could it be a issue with the way the nics are setup?
we have a setup consisting of:
1. physical instance of server 2008 SP3 R1 not part of a domain- running hyper-v with 5 Nics. 4 of them are in a balancing team which is assigned as an external network within hyper-v and the other one is the servers own NIC for remote admin.
2. Virtual instance of SBS2008 which is domain controller, exchange, DHCP, DNS server etc.
the issue is this... the SBS is unable to connect to the internet. i have no idea why but it can access and ping the internal network.. it says that it has internet connectivity but you cannot reach the internet or ping any external addresses. it did work on setup at the weekend but has dropped today.
why would this happen?
on the physical server in the network and sharing centre it states that the connection only has local connectivity so i assume the issue is there but why could this happen? could it be a issue with the way the nics are setup?
ASKER
sorry i meant sp1.
the sbs server can ping default gateway and other machines.
in the physical server 2008 there is 2 network connections. 1 which consists of a team which is assigned to the hyper-v and the other one is being used by the server
the sbs server can ping default gateway and other machines.
in the physical server 2008 there is 2 network connections. 1 which consists of a team which is assigned to the hyper-v and the other one is being used by the server
ASKER
when i say its being used by the server i mean it is being used by the physical server 2008
The 4 nic team is being used for the Hyper-V external network.
Just so you are aware, MS will not support you if you use teams for Hyper-V.
That aside, when you say a balancing team, do you mean e.g. smart load balancing or is it LACP (Link aggreation /802.3ad) team. Also, are there VLANs configured and are the VMs tagged in their NICs?
Are the VMs in the same IP Subnet as the host/physical switch/firewall etc.
Just so you are aware, MS will not support you if you use teams for Hyper-V.
That aside, when you say a balancing team, do you mean e.g. smart load balancing or is it LACP (Link aggreation /802.3ad) team. Also, are there VLANs configured and are the VMs tagged in their NICs?
Are the VMs in the same IP Subnet as the host/physical switch/firewall etc.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
correction cannot ping the gateway!
i think this has to do with the fact that sthe server 2008 has 2 ip addresses (1 for hyper v and 1 for the server itself)
if i team all the nics into one team will it effect server manageability?
i think this has to do with the fact that sthe server 2008 has 2 ip addresses (1 for hyper v and 1 for the server itself)
if i team all the nics into one team will it effect server manageability?
Which server has 2 IP addresses – the Hyper-V or the Virtual machine?
Basically, in such design we choose one NIC on the physical server for management only (without creating a virtual adapter from it) and another for the virtual traffic only. You need to clear “Allow management operation system…” for that virtual adapter in Virtual Network Manager as it is shown in the attachment
5-05-2011-9-21-45-AM.png
Basically, in such design we choose one NIC on the physical server for management only (without creating a virtual adapter from it) and another for the virtual traffic only. You need to clear “Allow management operation system…” for that virtual adapter in Virtual Network Manager as it is shown in the attachment
5-05-2011-9-21-45-AM.png
ASKER
hi,
the above is only relevent to server 2008 R2 as the management facility is not available on R1
they hyper-v has the 2 addresses
the above is only relevent to server 2008 R2 as the management facility is not available on R1
they hyper-v has the 2 addresses
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Btw, there is no Windows Server 2008 SP3 R1.