>
>
> "Bruce Sanderson" <(email address - cut out)am> wrote in message
> news:#(email address - cut out)...
>> Windows Server 2008 with Hyper-V installed.
>> I'm trying to follow the "best practice" of having one network adapter
>> for the "host" and a second one for the guest virtual machines.
>>
>> The server has two physical network adapters:
>> Broadcom NetXtreme Gigabit Ethernet
>> Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client
>>
>> I've configured the Broadcom BCM5708C to be the "host" network adapter -
>> that is working fine - it operates on the physical network just fine.
>>
>> However, I can not get the virtual machines to communicate with the
>> physical network using the second network adapter.
>>
>> Before starting to configure the Virtual Network, in Control Panel,
>> Network Connections, in the "Networking" tab of the Properties for the
>> other physical adapter (Broadcom NetXtreme Gigabit Ethernet), all the
>> check boxes are empty.
>>
>> In the Hyper-V Management Console:
>> 1. click Virtual Network Manager
>> 2. click New Virtual Network
>> 3. select External (default); click Add
>> 4. in Name: key "External"; in Connection Type: select External
>> (default); select Broadcom NetXtreme Gigabit Ethernet (default); click
>> Apply
>> 5. on the Apply Network Changes box warning about possible network
>> connectivity issues click Yes
>> 6. no error messages so assume the Virtual Network was created
>> successfully
>> 7. in Control Panel, Network, a third "connection" appeared - "Local Area
>> Connection 2"; Status = Enabled; Device Name=External
>> 8. In Control Panel, Network Connections, in the "Networking" tab of the
>> Properties for the Broadcom NetXtreme Gigabit Ethernet adapter, there is
>> now a check mark beside Microsoft Virtual Network Switch Protocol - there
>> are no other check marks
>> 9. in Control Panel, Network Connections, in the "Networking" tab of the
>> Properties for "Local Area Connection 2", there are no check marks at all
>> 10. Create a virtual machine and install Windows Server 2008 in it;
>> install the "Integration Services" . In the Virtual Machine "Settings",
>> for Network Adapter, for "Network" select "External"
>> 11. logon to the virtual machine; on the Intital Configuration Tasks
>> panel, click Configure Networking, which opens Control Panel, Network
>> Connections - the Status remains at "Identifying"; icpconfig command
>> shows
>> DHCP Enabled Yes
>> Autoconfiguration Enabled Yes
>> Autoconfiguration IPv4 Address 169.254.24.83 (Preferred)
>> Subnet Mask 255.255.0.0
>> Default Gateway:
>> NetBIOS over TCP/IP Enabled
>>
>> 12. in Control Panel, Network Connections, right click Local Area
>> Network, select Properties
>> 12.a. click Internet Protocol Version 4 (TCP/IPv4), click Properties
>> 12.b. select the Use the following IP address: radio button
>> IP Address: 142.31.131.202
>> Subnet mask: 255.255.255.128
>> Default Gateway: 142.31.131.129
>> 12.c. key:
>> Primary DNS server: 142.32.208.196
>> Secondary DNS server: 142.22.44.132
>>
>> Note: this is the same as the "host" network adapter except that the IP
>> Address for the "host" is 142.31.131.201. Both physical network adapters
>> are wired to the same switch.
>>
>> 12.d. click OK; click Close
>> 13. in Control Panel, Network Connections, status goes to Unidentified
>> Network; "Connectivity" stays at "Limited connectivity"
>>
>> As far as I can tell, this Virtual Machine can not communicate with
>> anything on the network at all.
>>
>> So, what do I need to do to get this "recommended" network setup to work?
>> I've looked in various places for documentation, but can not find any
>> details about how to set this up, just that it is a "best practice".
>>
>> --
>> Bruce Sanderson
>> http://members.shaw.ca/bsanders/
>> It's perfectly useless to know the right answer to the wrong question.
>>
>>
>
> Hi Bruce,
>
> That should be all you need to do. There were some problems with the
> Broadcomm drivers not working properly with the virtual switch software
> but I thought that had been sorted out. You could try disabling TCP
> offload on the NIC (as that seemed to be the problem).
>
> It is probably work switching things around and running the "other"
> NIC as the connection to the virtual switch to check if it is just
> something odd with the driver software.
>
>

> OK Thanks, Bill. I'll try what you suggest and reply with the result.
>
> --
> Bruce Sanderson
> http://members.shaw.ca/bsanders/
> It's perfectly useless to know the right answer to the wrong question.
>
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
>>
>>
>> "Bruce Sanderson" <(email address - cut out)am> wrote in message
>> news:#(email address - cut out)...
>>> Windows Server 2008 with Hyper-V installed.
>>> I'm trying to follow the "best practice" of having one network adapter
>>> for the "host" and a second one for the guest virtual machines.
>>>
>>> The server has two physical network adapters:
>>> Broadcom NetXtreme Gigabit Ethernet
>>> Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client
>>>
>>> I've configured the Broadcom BCM5708C to be the "host" network adapter -
>>> that is working fine - it operates on the physical network just fine.
>>>
>>> However, I can not get the virtual machines to communicate with the
>>> physical network using the second network adapter.
>>>
>>> Before starting to configure the Virtual Network, in Control Panel,
>>> Network Connections, in the "Networking" tab of the Properties for the
>>> other physical adapter (Broadcom NetXtreme Gigabit Ethernet), all the
>>> check boxes are empty.
>>>
>>> In the Hyper-V Management Console:
>>> 1. click Virtual Network Manager
>>> 2. click New Virtual Network
>>> 3. select External (default); click Add
>>> 4. in Name: key "External"; in Connection Type: select External
>>> (default); select Broadcom NetXtreme Gigabit Ethernet (default); click
>>> Apply
>>> 5. on the Apply Network Changes box warning about possible network
>>> connectivity issues click Yes
>>> 6. no error messages so assume the Virtual Network was created
>>> successfully
>>> 7. in Control Panel, Network, a third "connection" appeared - "Local
>>> Area Connection 2"; Status = Enabled; Device Name=External
>>> 8. In Control Panel, Network Connections, in the "Networking" tab of the
>>> Properties for the Broadcom NetXtreme Gigabit Ethernet adapter, there is
>>> now a check mark beside Microsoft Virtual Network Switch Protocol -
>>> there are no other check marks
>>> 9. in Control Panel, Network Connections, in the "Networking" tab of the
>>> Properties for "Local Area Connection 2", there are no check marks at
>>> all
>>> 10. Create a virtual machine and install Windows Server 2008 in it;
>>> install the "Integration Services" . In the Virtual Machine "Settings",
>>> for Network Adapter, for "Network" select "External"
>>> 11. logon to the virtual machine; on the Intital Configuration Tasks
>>> panel, click Configure Networking, which opens Control Panel, Network
>>> Connections - the Status remains at "Identifying"; icpconfig command
>>> shows
>>> DHCP Enabled Yes
>>> Autoconfiguration Enabled Yes
>>> Autoconfiguration IPv4 Address 169.254.24.83 (Preferred)
>>> Subnet Mask 255.255.0.0
>>> Default Gateway:
>>> NetBIOS over TCP/IP Enabled
>>>
>>> 12. in Control Panel, Network Connections, right click Local Area
>>> Network, select Properties
>>> 12.a. click Internet Protocol Version 4 (TCP/IPv4), click Properties
>>> 12.b. select the Use the following IP address: radio button
>>> IP Address: 142.31.131.202
>>> Subnet mask: 255.255.255.128
>>> Default Gateway: 142.31.131.129
>>> 12.c. key:
>>> Primary DNS server: 142.32.208.196
>>> Secondary DNS server: 142.22.44.132
>>>
>>> Note: this is the same as the "host" network adapter except that the IP
>>> Address for the "host" is 142.31.131.201. Both physical network
>>> adapters are wired to the same switch.
>>>
>>> 12.d. click OK; click Close
>>> 13. in Control Panel, Network Connections, status goes to Unidentified
>>> Network; "Connectivity" stays at "Limited connectivity"
>>>
>>> As far as I can tell, this Virtual Machine can not communicate with
>>> anything on the network at all.
>>>
>>> So, what do I need to do to get this "recommended" network setup to
>>> work? I've looked in various places for documentation, but can not find
>>> any details about how to set this up, just that it is a "best practice".
>>>
>>> --
>>> Bruce Sanderson
>>> http://members.shaw.ca/bsanders/
>>> It's perfectly useless to know the right answer to the wrong question.
>>>
>>>
>>
>> Hi Bruce,
>>
>> That should be all you need to do. There were some problems with the
>> Broadcomm drivers not working properly with the virtual switch software
>> but I thought that had been sorted out. You could try disabling TCP
>> offload on the NIC (as that seemed to be the problem).
>>
>> It is probably work switching things around and running the "other"
>> NIC as the connection to the virtual switch to check if it is just
>> something odd with the driver software.
>>
>>

> Windows Server 2008 with Hyper-V installed.
> I'm trying to follow the "best practice" of having one network adapter for
> the "host" and a second one for the guest virtual machines.
>
> The server has two physical network adapters:
> Broadcom NetXtreme Gigabit Ethernet
> Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client
>
> I've configured the Broadcom BCM5708C to be the "host" network adapter -
> that is working fine - it operates on the physical network just fine.
>
> However, I can not get the virtual machines to communicate with the
> physical network using the second network adapter.
>
> Before starting to configure the Virtual Network, in Control Panel,
> Network Connections, in the "Networking" tab of the Properties for the
> other physical adapter (Broadcom NetXtreme Gigabit Ethernet), all the
> check boxes are empty.
>
> In the Hyper-V Management Console:
> 1. click Virtual Network Manager
> 2. click New Virtual Network
> 3. select External (default); click Add
> 4. in Name: key "External"; in Connection Type: select External (default);
> select Broadcom NetXtreme Gigabit Ethernet (default); click Apply
> 5. on the Apply Network Changes box warning about possible network
> connectivity issues click Yes
> 6. no error messages so assume the Virtual Network was created
> successfully
> 7. in Control Panel, Network, a third "connection" appeared - "Local Area
> Connection 2"; Status = Enabled; Device Name=External
> 8. In Control Panel, Network Connections, in the "Networking" tab of the
> Properties for the Broadcom NetXtreme Gigabit Ethernet adapter, there is
> now a check mark beside Microsoft Virtual Network Switch Protocol - there
> are no other check marks
> 9. in Control Panel, Network Connections, in the "Networking" tab of the
> Properties for "Local Area Connection 2", there are no check marks at all
> 10. Create a virtual machine and install Windows Server 2008 in it;
> install the "Integration Services" . In the Virtual Machine "Settings",
> for Network Adapter, for "Network" select "External"
> 11. logon to the virtual machine; on the Intital Configuration Tasks
> panel, click Configure Networking, which opens Control Panel, Network
> Connections - the Status remains at "Identifying"; icpconfig command shows
> DHCP Enabled Yes
> Autoconfiguration Enabled Yes
> Autoconfiguration IPv4 Address 169.254.24.83 (Preferred)
> Subnet Mask 255.255.0.0
> Default Gateway:
> NetBIOS over TCP/IP Enabled
>
> 12. in Control Panel, Network Connections, right click Local Area Network,
> select Properties
> 12.a. click Internet Protocol Version 4 (TCP/IPv4), click Properties
> 12.b. select the Use the following IP address: radio button
> IP Address: 142.31.131.202
> Subnet mask: 255.255.255.128
> Default Gateway: 142.31.131.129
> 12.c. key:
> Primary DNS server: 142.32.208.196
> Secondary DNS server: 142.22.44.132
>
> Note: this is the same as the "host" network adapter except that the IP
> Address for the "host" is 142.31.131.201. Both physical network adapters
> are wired to the same switch.
>
> 12.d. click OK; click Close
> 13. in Control Panel, Network Connections, status goes to Unidentified
> Network; "Connectivity" stays at "Limited connectivity"
>
> As far as I can tell, this Virtual Machine can not communicate with
> anything on the network at all.
>
> So, what do I need to do to get this "recommended" network setup to work?
> I've looked in various places for documentation, but can not find any
> details about how to set this up, just that it is a "best practice".
>
> --
> Bruce Sanderson
> http://members.shaw.ca/bsanders/
> It's perfectly useless to know the right answer to the wrong question.
>
>

> Windows Server 2008 with Hyper-V installed.
> I'm trying to follow the "best practice" of having one network adapter for the "host" and a second
> one for the guest virtual machines.
>
> The server has two physical network adapters:
> Broadcom NetXtreme Gigabit Ethernet
> Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client
>
> I've configured the Broadcom BCM5708C to be the "host" network adapter - that is working fine - it
> operates on the physical network just fine.
>
> However, I can not get the virtual machines to communicate with the physical network using the
> second network adapter.
>
> Before starting to configure the Virtual Network, in Control Panel, Network Connections, in the
> "Networking" tab of the Properties for the other physical adapter (Broadcom NetXtreme Gigabit
> Ethernet), all the check boxes are empty.
>
> In the Hyper-V Management Console:
> 1. click Virtual Network Manager
> 2. click New Virtual Network
> 3. select External (default); click Add
> 4. in Name: key "External"; in Connection Type: select External (default); select Broadcom NetXtreme
> Gigabit Ethernet (default); click Apply
> 5. on the Apply Network Changes box warning about possible network connectivity issues click Yes
> 6. no error messages so assume the Virtual Network was created successfully
> 7. in Control Panel, Network, a third "connection" appeared - "Local Area Connection 2"; Status =
> Enabled; Device Name=External
> 8. In Control Panel, Network Connections, in the "Networking" tab of the Properties for the Broadcom
> NetXtreme Gigabit Ethernet adapter, there is now a check mark beside Microsoft Virtual Network
> Switch Protocol - there are no other check marks
> 9. in Control Panel, Network Connections, in the "Networking" tab of the Properties for "Local Area
> Connection 2", there are no check marks at all
> 10. Create a virtual machine and install Windows Server 2008 in it; install the "Integration
> Services" . In the Virtual Machine "Settings", for Network Adapter, for "Network" select "External"
> 11. logon to the virtual machine; on the Intital Configuration Tasks panel, click Configure
> Networking, which opens Control Panel, Network Connections - the Status remains at "Identifying";
> icpconfig command shows
> DHCP Enabled Yes
> Autoconfiguration Enabled Yes
> Autoconfiguration IPv4 Address 169.254.24.83 (Preferred)
> Subnet Mask 255.255.0.0
> Default Gateway:
> NetBIOS over TCP/IP Enabled
>
> 12. in Control Panel, Network Connections, right click Local Area Network, select Properties
> 12.a. click Internet Protocol Version 4 (TCP/IPv4), click Properties
> 12.b. select the Use the following IP address: radio button
> IP Address: 142.31.131.202
> Subnet mask: 255.255.255.128
> Default Gateway: 142.31.131.129
> 12.c. key:
> Primary DNS server: 142.32.208.196
> Secondary DNS server: 142.22.44.132
>
> Note: this is the same as the "host" network adapter except that the IP Address for the "host" is
> 142.31.131.201. Both physical network adapters are wired to the same switch.
>
> 12.d. click OK; click Close
> 13. in Control Panel, Network Connections, status goes to Unidentified Network; "Connectivity" stays
> at "Limited connectivity"
>
> As far as I can tell, this Virtual Machine can not communicate with anything on the network at all.
>
> So, what do I need to do to get this "recommended" network setup to work? I've looked in various
> places for documentation, but can not find any details about how to set this up, just that it is a
> "best practice".
>
> --
> Bruce Sanderson
> http://members.shaw.ca/bsanders/
> It's perfectly useless to know the right answer to the wrong question.
>