> Hi all,
>
> I am still having trouble getting Vista x64 to gain access to the Internet
> as a Guest within Hyper-V on WinSrv 2008. I have set up a legacy adapter
> off of an internal type NIC in the VM Settings, I started the guest Vista
> x64, but it still says limited connectivity. It just says "Limited
> connectivity" to a "unidentified network" which has non access to the
> Internet, in the graphical picture at Network and Sharing Center. I know
> there is no Integration Services support for Vista x64 at this time, I
> read this was the way to set up network access.
>
> What am I doing wrong?

> The problem is that you chose an "internal" NIC type. There are three
> types of network connections: External, Internal, and Private. External
> passes through to the Internet, Internal only allows connections to the
> host and other VMs on that network, Private allows connections only to
> other VMs on that machine and on that network.
>

> Charlie Russel - MVP wrote:
>> The problem is that you chose an "internal" NIC type. There are three
>> types of network connections: External, Internal, and Private. External
>> passes through to the Internet, Internal only allows connections to the
>> host and other VMs on that network, Private allows connections only to
>> other VMs on that machine and on that network.
>>
> I tried External first, but when I start the VM it just says "Windows
> cannot find any networks". When I view network computers and devices just
> itself is there, and it says click to connect to a network, but then I go
> back and there is no network to connect to.

> Charlie Russel - MVP wrote:
>> you need to connect the external NIC type to a "legacy network adapter",
>> not a "network adapter". There is no support for the synthetic network
>> adapter in Vista 64, you have to use the legacy emulation one.
>>
> Sorry I am having trouble with this, I have read the startup doc and tried
> to read other posts but I have not find a clear description of this
> process.
>
> Here is what I did after I deleted all network support so I could start
> over:
>
> 1. On my Host (WinSrv2008) machine's local area connection, I went into
> properties and checked "Microsoft Network Switch Protocol".
>
> 2. In Hyper-V Manager, under Virtual Network Manager, (which shows no
> virtual networks), I highlight External and click Add. External rasdio
> button is selected, I make sure the NIC is my active one (there is a
> disabled on-system board NIC which should not be selected). I leave Enable
> Virtual LAN identification unchecked. I click OK.
>
> At that point, I get "Error applying New Virtual Network Changes". Setup
> Switch failed. The switch could not bind to <NIC card> because it is
> already bound to another switch."
>
> 3. So I go back and reverse #1, unchecking "Microsoft network switch
> protocol". Which I don't understand since the description says "Provides
> network connectivity to virtual machine partitions". ???
>
> Also - after I then try step 2, which is now accepted, my existing local
> network connection has ONLY "Microsoft network switch protocol" checked,
> and a new connection which connects using Virtual Network and NOT my NIC,
> has the options checked of my original NIC. I tried opening IE and it
> works (on the host), so I guess this is right. But I don't understand it.
>
> 4. .So now back in Hyper-V Manager, I select Settings for my VM (a Vista
> x64 guest). I make sure no networks exist, I click on Add Hardware. I
> click Legacy Network Adapter then Add. The combo box under Network: says
> Not connected, I pick New Virtual Network (which was the default name I
> accepted from Step 2.) I left everything else in its default state, and
> click OK.
>
> 5. I click Start on the VM. I wait a bit, and check the network icon in
> the system tray. It says "Currently Connected to Unidentified network"
> Access: Local Only. I click on View Networks and Computers, and I only see
> the Guest, the host, and one other WinSrv 2008 computer on the network
> (there are about 6 other computers on this network). Network and Sharing
> Center shows Guest connected to Unidentified Network, from there through a
> red "X" to the Internet. I tried repairing by clicking on the red "X" and
> that did not work.
>
> So what did I do wrong, and what's the best document to read about the
> stuff it did to my Host network connections, and how "Microsoft network
> switch protocol" works?
>
> Thanks..

> you need to connect the external NIC type to a "legacy network adapter",
> not a "network adapter". There is no support for the synthetic network
> adapter in Vista 64, you have to use the legacy emulation one.
>

> 1.) You do NOT do that. That will be managed by Hyper-V and the OS. Do
> not directly configure anything on the Parent Partition NICs. Except set
> a fixed IP if you need to, but even there I usually don't, since that's
> going to go away. When you get done, the original NIC won't have an IP
> address at all. That's why the instructions tell you to always leave one
> available to connect to.
>
> 2.) The normal process of adding the Role will create your first
> network. If you do what you did, you'll fail, as you did.
>
> I strongly suggest you start over. I don't know WHAT you've done. And I
> doubt any more that you do. I would start by uninstalling the Hyper-V
> role, or building the machine from scratch. Configure your NICs for
> normal operation. (You should have at LEAST two NICs in any server that
> will be running Hyper-V, IMHO.)
>
> Next, install any additional Roles or Features you'll need on the
> server. (note that the recommendation is to run Hyper-V as the only Role
> on the server in any production situation.
>
> Now, Install the Role. When prompted by the installation wizard, let the
> Add Roles Wizard create your original network(s). Leave one network card
> for connecting to the server to manage it.
>
> Once you have the Role installed, you can add any additional networks.
> External networks require binding to a NIC and taking it over, leaving
> the original ONLY running the switch protocol, and creating a new
> network switch that has everything else on it.
>
> For machines that require access to networking, but that don't have
> Integration Components available, you'll need to create the VM and add a
> Legacy NIC, connecting to the appropriate virtual network.
>
> All this is covered in its own chapter in my book, by the way -
> Microsoft Windows Server 2008 Administrator's Companion (MS Press).
> Which should be just getting to stores now.
>

> 1.) You do NOT do that. That will be managed by Hyper-V and the OS. Do
> not directly configure anything on the Parent Partition NICs. Except set
> a fixed IP if you need to, but even there I usually don't, since that's
> going to go away. When you get done, the original NIC won't have an IP
> address at all. That's why the instructions tell you to always leave one
> available to connect to.
>
> 2.) The normal process of adding the Role will create your first
> network. If you do what you did, you'll fail, as you did.
>
> I strongly suggest you start over. I don't know WHAT you've done. And I
> doubt any more that you do. I would start by uninstalling the Hyper-V
> role, or building the machine from scratch. Configure your NICs for
> normal operation. (You should have at LEAST two NICs in any server that
> will be running Hyper-V, IMHO.)
>
> Next, install any additional Roles or Features you'll need on the
> server. (note that the recommendation is to run Hyper-V as the only Role
> on the server in any production situation.
>
> Now, Install the Role. When prompted by the installation wizard, let the
> Add Roles Wizard create your original network(s). Leave one network card
> for connecting to the server to manage it.
>
> Once you have the Role installed, you can add any additional networks.
> External networks require binding to a NIC and taking it over, leaving
> the original ONLY running the switch protocol, and creating a new
> network switch that has everything else on it.
>
> For machines that require access to networking, but that don't have
> Integration Components available, you'll need to create the VM and add a
> Legacy NIC, connecting to the appropriate virtual network.
>
> All this is covered in its own chapter in my book, by the way -
> Microsoft Windows Server 2008 Administrator's Companion (MS Press).
> Which should be just getting to stores now.
>

> You need to connect the NIC in your Vista OS to the external virtual
> network which is linked to one of the physical NICs of the host if you
> want direct access to the Internet.
>
> How does your host machine get its network config? From DHCP? Your
> Vista machine should be able to do the same, but I have heard of people
> having problems getting network config for a vm from a DHCP server on
> the LAN with hyper-V.
>
> Do an ipconfig /all on the Vista machine to see what config it has.
> If it has an APIPA address (169.254.x.x) try setting its config manually
> to match the config of the host.
>
> "Dominick" <(email address - cut out)> wrote in message
> news:%23bX$(email address - cut out)...
>> Charlie Russel - MVP wrote:
>>> 1.) You do NOT do that. That will be managed by Hyper-V and the OS.
>>> Do not directly configure anything on the Parent Partition NICs.
>>> Except set a fixed IP if you need to, but even there I usually don't,
>>> since that's going to go away. When you get done, the original NIC
>>> won't have an IP address at all. That's why the instructions tell you
>>> to always leave one available to connect to.
>>>
>>> 2.) The normal process of adding the Role will create your first
>>> network. If you do what you did, you'll fail, as you did.
>>>
>>> I strongly suggest you start over. I don't know WHAT you've done. And
>>> I doubt any more that you do. I would start by uninstalling the
>>> Hyper-V role, or building the machine from scratch. Configure your
>>> NICs for normal operation. (You should have at LEAST two NICs in any
>>> server that will be running Hyper-V, IMHO.)
>>>
>>> Next, install any additional Roles or Features you'll need on the
>>> server. (note that the recommendation is to run Hyper-V as the only
>>> Role on the server in any production situation.
>>>
>>> Now, Install the Role. When prompted by the installation wizard, let
>>> the Add Roles Wizard create your original network(s). Leave one
>>> network card for connecting to the server to manage it.
>>>
>>> Once you have the Role installed, you can add any additional
>>> networks. External networks require binding to a NIC and taking it
>>> over, leaving the original ONLY running the switch protocol, and
>>> creating a new network switch that has everything else on it.
>>>
>>> For machines that require access to networking, but that don't have
>>> Integration Components available, you'll need to create the VM and
>>> add a Legacy NIC, connecting to the appropriate virtual network.
>>>
>>> All this is covered in its own chapter in my book, by the way -
>>> Microsoft Windows Server 2008 Administrator's Companion (MS Press).
>>> Which should be just getting to stores now.
>>>
>> I have gone through this, and I think I have it right now. I have a
>> machine with two physical NICs, it added a third virtual one and
>> turned everything off on one of the two physical ones except the
>> switch. I see in the Virtual Network Manager an External virtual
>> network tied tow one of my two physical NICs.
>>
>> I have a virtual machine with Vista x64 installed (the Host OS is
>> WinSrv 2008 x64). In the guest VM's settings, since there are no
>> Integration Services, there is a Legacy Network adapter tied to the
>> virtual network created in my Host network connections that displays
>> alongside the two physical NICs.
>>
>> However - I still do not have connectivity. In the system tray of the
>> Guest OS it says "Unidentified Network" with limited connectivity. It
>> does not see any networks to connect to. Network and Sharing Center
>> shows the Guest OS machine connected to "Unidentified Network" with a
>> yellow triangular icon in between, that says "Click to diagnose" if
>> you hover over it. Unidentified Network is connected to the Internet
>> with a big red 'X'.
>>
>> I am really starting to think that this is because I am using Vista
>> x64, that in the RC 0 that just doesn't work. I haven't found anyone
>> talking about that setup other than the obvious stuff like "use a
>> legacy adapter if there are no Integration Services, etc. Has anyone
>> actually done this combination?
>>
>> Any ideas on how to diagnose the problem, what to look at, etc. would
>> be appreciated. Otherwise I guess I am forced to wait for Integration
>> services and the final release...
>

> Charlie Russel - MVP wrote:
>> 1.) You do NOT do that. That will be managed by Hyper-V and the OS. Do
>> not directly configure anything on the Parent Partition NICs. Except set
>> a fixed IP if you need to, but even there I usually don't, since that's
>> going to go away. When you get done, the original NIC won't have an IP
>> address at all. That's why the instructions tell you to always leave one
>> available to connect to.
>>
>> 2.) The normal process of adding the Role will create your first network.
>> If you do what you did, you'll fail, as you did.
>>
>> I strongly suggest you start over. I don't know WHAT you've done. And I
>> doubt any more that you do. I would start by uninstalling the Hyper-V
>> role, or building the machine from scratch. Configure your NICs for
>> normal operation. (You should have at LEAST two NICs in any server that
>> will be running Hyper-V, IMHO.)
>>
>> Next, install any additional Roles or Features you'll need on the server.
>> (note that the recommendation is to run Hyper-V as the only Role on the
>> server in any production situation.
>>
>> Now, Install the Role. When prompted by the installation wizard, let the
>> Add Roles Wizard create your original network(s). Leave one network card
>> for connecting to the server to manage it.
>>
>> Once you have the Role installed, you can add any additional networks.
>> External networks require binding to a NIC and taking it over, leaving
>> the original ONLY running the switch protocol, and creating a new network
>> switch that has everything else on it.
>>
>> For machines that require access to networking, but that don't have
>> Integration Components available, you'll need to create the VM and add a
>> Legacy NIC, connecting to the appropriate virtual network.
>>
>> All this is covered in its own chapter in my book, by the way - Microsoft
>> Windows Server 2008 Administrator's Companion (MS Press). Which should be
>> just getting to stores now.
>>
> I have gone through this, and I think I have it right now. I have a
> machine with two physical NICs, it added a third virtual one and turned
> everything off on one of the two physical ones except the switch. I see in
> the Virtual Network Manager an External virtual network tied tow one of my
> two physical NICs.
>
> I have a virtual machine with Vista x64 installed (the Host OS is WinSrv
> 2008 x64). In the guest VM's settings, since there are no Integration
> Services, there is a Legacy Network adapter tied to the virtual network
> created in my Host network connections that displays alongside the two
> physical NICs.
>
> However - I still do not have connectivity. In the system tray of the
> Guest OS it says "Unidentified Network" with limited connectivity. It does
> not see any networks to connect to. Network and Sharing Center shows the
> Guest OS machine connected to "Unidentified Network" with a yellow
> triangular icon in between, that says "Click to diagnose" if you hover
> over it. Unidentified Network is connected to the Internet with a big red
> 'X'.
>
> I am really starting to think that this is because I am using Vista x64,
> that in the RC 0 that just doesn't work. I haven't found anyone talking
> about that setup other than the obvious stuff like "use a legacy adapter
> if there are no Integration Services, etc. Has anyone actually done this
> combination?
>
> Any ideas on how to diagnose the problem, what to look at, etc. would be
> appreciated. Otherwise I guess I am forced to wait for Integration
> services and the final release...

> Bill Grant wrote:
>> You need to connect the NIC in your Vista OS to the external virtual
>> network which is linked to one of the physical NICs of the host if you
>> want direct access to the Internet.
>>
>> How does your host machine get its network config? From DHCP? Your
>> Vista machine should be able to do the same, but I have heard of people
>> having problems getting network config for a vm from a DHCP server on the
>> LAN with hyper-V.
>>
>> Do an ipconfig /all on the Vista machine to see what config it has. If
>> it has an APIPA address (169.254.x.x) try setting its config manually to
>> match the config of the host.
>>
>> "Dominick" <(email address - cut out)> wrote in message
>> news:%23bX$(email address - cut out)...
>>> Charlie Russel - MVP wrote:
>>>> 1.) You do NOT do that. That will be managed by Hyper-V and the OS. Do
>>>> not directly configure anything on the Parent Partition NICs. Except
>>>> set a fixed IP if you need to, but even there I usually don't, since
>>>> that's going to go away. When you get done, the original NIC won't have
>>>> an IP address at all. That's why the instructions tell you to always
>>>> leave one available to connect to.
>>>>
>>>> 2.) The normal process of adding the Role will create your first
>>>> network. If you do what you did, you'll fail, as you did.
>>>>
>>>> I strongly suggest you start over. I don't know WHAT you've done. And I
>>>> doubt any more that you do. I would start by uninstalling the Hyper-V
>>>> role, or building the machine from scratch. Configure your NICs for
>>>> normal operation. (You should have at LEAST two NICs in any server that
>>>> will be running Hyper-V, IMHO.)
>>>>
>>>> Next, install any additional Roles or Features you'll need on the
>>>> server. (note that the recommendation is to run Hyper-V as the only
>>>> Role on the server in any production situation.
>>>>
>>>> Now, Install the Role. When prompted by the installation wizard, let
>>>> the Add Roles Wizard create your original network(s). Leave one network
>>>> card for connecting to the server to manage it.
>>>>
>>>> Once you have the Role installed, you can add any additional networks.
>>>> External networks require binding to a NIC and taking it over, leaving
>>>> the original ONLY running the switch protocol, and creating a new
>>>> network switch that has everything else on it.
>>>>
>>>> For machines that require access to networking, but that don't have
>>>> Integration Components available, you'll need to create the VM and add
>>>> a Legacy NIC, connecting to the appropriate virtual network.
>>>>
>>>> All this is covered in its own chapter in my book, by the way -
>>>> Microsoft Windows Server 2008 Administrator's Companion (MS Press).
>>>> Which should be just getting to stores now.
>>>>
>>> I have gone through this, and I think I have it right now. I have a
>>> machine with two physical NICs, it added a third virtual one and turned
>>> everything off on one of the two physical ones except the switch. I see
>>> in the Virtual Network Manager an External virtual network tied tow one
>>> of my two physical NICs.
>>>
>>> I have a virtual machine with Vista x64 installed (the Host OS is WinSrv
>>> 2008 x64). In the guest VM's settings, since there are no Integration
>>> Services, there is a Legacy Network adapter tied to the virtual network
>>> created in my Host network connections that displays alongside the two
>>> physical NICs.
>>>
>>> However - I still do not have connectivity. In the system tray of the
>>> Guest OS it says "Unidentified Network" with limited connectivity. It
>>> does not see any networks to connect to. Network and Sharing Center
>>> shows the Guest OS machine connected to "Unidentified Network" with a
>>> yellow triangular icon in between, that says "Click to diagnose" if you
>>> hover over it. Unidentified Network is connected to the Internet with a
>>> big red 'X'.
>>>
>>> I am really starting to think that this is because I am using Vista x64,
>>> that in the RC 0 that just doesn't work. I haven't found anyone talking
>>> about that setup other than the obvious stuff like "use a legacy adapter
>>> if there are no Integration Services, etc. Has anyone actually done this
>>> combination?
>>>
>>> Any ideas on how to diagnose the problem, what to look at, etc. would be
>>> appreciated. Otherwise I guess I am forced to wait for Integration
>>> services and the final release...
>>
> I think that did it! Yes, the Host uses DHCP, and the Guest OS had an
> APIPA address. So I changed the setting manually to match the virtual
> connection the Hyper-V setup created in the Host, and then it appeared to
> change its status to having a good network; BUT, it then complained about
> an IP address conflict. Was this because it should not match the virtual
> connection in the Host's IP address? Or I bet that might have been because
> that NIC existing as a normal connection before Hyper-V grabbed it, so
> there was a DNS entry for that IP with the Host OS computer's name?
>
> Anyway - I just manually changed the IP address to one in range that I
> knew wasn't taken. And it all works! So clearly the problem has been that
> Vista x64 as Guest is getting a DHCP-generated address on my network.
>
> Should the manual IP address have matched the virtual IP address on the
> Host OS? Or should I have used another address?

> you use another address.
>
> DHCP should work - it certainly does here for my Vista 64 clients. And
> the DHCP server is my SBS box in one case, or another Hyper-V box in the
> other. However, expecting a consumer grade router's DHCP to work may be
> less successful - I've seen problems with that scenario.
>

> Charlie Russel - MVP wrote:
>> you use another address.
>>
>> DHCP should work - it certainly does here for my Vista 64 clients. And
>> the DHCP server is my SBS box in one case, or another Hyper-V box in the
>> other. However, expecting a consumer grade router's DHCP to work may be
>> less successful - I've seen problems with that scenario.
>>
> I am actually using Windows Server 2003 for DHCP. So I am not sure why it
> did not get a DHCP-issued IP address.
>
> So I just tried again, switching back to automatic for IP, and it got an
> IP address. The two only real changes since I manually set the IP address
> were (1) I became a member of the domain (it was the generic WORKGROUP)
> and (2) I updated about 58 updates to the Guest OS. Nothing else has
> really changed.

> Hi all,
>
> I am still having trouble getting Vista x64 to gain access to the
> Internet as a Guest within Hyper-V on WinSrv 2008. I have set up a
> legacy adapter off of an internal type NIC in the VM Settings, I started
> the guest Vista x64, but it still says limited connectivity. It just
> says "Limited connectivity" to a "unidentified network" which has non
> access to the Internet, in the graphical picture at Network and Sharing
> Center. I know there is no Integration Services support for Vista x64 at
> this time, I read this was the way to set up network access.
>
> What am I doing wrong?

>
>> Hi all,
>>
>> I am still having trouble getting Vista x64 to gain access to the
>> Internet as a Guest within Hyper-V on WinSrv 2008. I have set up a
>> legacy adapter off of an internal type NIC in the VM Settings, I started
>> the guest Vista x64, but it still says limited connectivity. It just
>> says "Limited connectivity" to a "unidentified network" which has non
>> access to the Internet, in the graphical picture at Network and Sharing
>> Center. I know there is no Integration Services support for Vista x64 at
>> this time, I read this was the way to set up network access.
>>
>> What am I doing wrong?
>
> I have read this thread and any others I can find but I have a different
> problem. I installed WS2008(64b), updated it with hyper-v. Created a role
> for hyper-v then installed vista(64b). When I get into vista there are no
> network devices. Went back to WS2008 checked it, back into vista checked
> it. What am I doing wrong???
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
> Information Technology Shop - http://www.bitshop.com

> Hi all,
>
> I am still having trouble getting Vista x64 to gain access to the
> Internet as a Guest within Hyper-V on WinSrv 2008. I have set up a
> legacy adapter off of an internal type NIC in the VM Settings, I started
> the guest Vista x64, but it still says limited connectivity. It just
> says "Limited connectivity" to a "unidentified network" which has non
> access to the Internet, in the graphical picture at Network and Sharing
> Center. I know there is no Integration Services support for Vista x64 at
> this time, I read this was the way to set up network access.
>
> What am I doing wrong?