ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Hyper-V 2016 (Switch) and NIC

    IT Discussion
    5
    10
    603
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JoelJ
      Joel
      last edited by

      So, I've built a HyperV server 2016 and have provisioned two VMS. All great so far, however I have a problem getting internet access to the VMs.

      Our HV host has internet access - all okay.
      I created a Hyper V Switch (external network), and then ensured the VM's virtual adapter is connected to the switch. However we get a 169. IP.

      On the host itself, if I enter SConfig and go to Network settings, I see two adapters (1 is the local NIC which has a valid IP), the other is my Hyper V Virtual Ethernet adapter with a 169. IP.

      I have tried giving it a Static but it still wont work!
      Any assistance would be appreciated. Thanks.

      matteo nunziatiM 1 Reply Last reply Reply Quote 0
      • black3dynamiteB
        black3dynamite
        last edited by

        On the HV host, which port is connected to the network?

        JoelJ 1 Reply Last reply Reply Quote 0
        • black3dynamiteB
          black3dynamite
          last edited by

          Your vswitch should be using the physical port that is active.

          JoelJ 1 Reply Last reply Reply Quote 1
          • JoelJ
            Joel @black3dynamite
            last edited by

            @black3dynamite

            Our host has 4 ports...Port 1 is connected directly to the router.
            We dont have anything else in port 2,3,4

            1 Reply Last reply Reply Quote 0
            • JoelJ
              Joel @black3dynamite
              last edited by

              @black3dynamite It is

              JoelJ 1 Reply Last reply Reply Quote 0
              • JoelJ
                Joel @Joel
                last edited by

                @joel said in Hyper-V 2016 (Switch) and NIC:

                @black3dynamite Your vswitch should be using the physical port that is active.

                It is

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @Joel
                  last edited by

                  @joel said in Hyper-V 2016 (Switch) and NIC:

                  @joel said in Hyper-V 2016 (Switch) and NIC:

                  @black3dynamite Your vswitch should be using the physical port that is active.

                  It is

                  It obviously is not configured correctly somewhere.

                  As you can see here, my vSwitch is setup to use the Multiplexor NIC. This is the Team I setup. This is no different than selecting a single NIC.
                  0_1534521668472_deda9205-874f-4eb7-a870-455980d27d19-image.png

                  Here you can see I have all the NICs in a team. So that Multiplexor is the only choice I have for the vSwitch.
                  0_1534521639315_90004649-205f-4f15-857b-ba1a87ef7a15-image.png

                  1 Reply Last reply Reply Quote 0
                  • J
                    Jimmy9008
                    last edited by

                    169.x.x.x shouts out that the VM cant reach a DHCP server. If the vSwitch is using the active interface, and allows guest VMs to share the adapter, i'd check if my DHCP server is ok, on the same network, has IPs available etc. The host would be static so thats why that would be working as it was manually configured.

                    JoelJ 1 Reply Last reply Reply Quote 1
                    • matteo nunziatiM
                      matteo nunziati @Joel
                      last edited by

                      @joel said in Hyper-V 2016 (Switch) and NIC:

                      So, I've built a HyperV server 2016 and have provisioned two VMS. All great so far, however I have a problem getting internet access to the VMs.

                      Our HV host has internet access - all okay.
                      I created a Hyper V Switch (external network), and then ensured the VM's virtual adapter is connected to the switch. However we get a 169. IP.

                      On the host itself, if I enter SConfig and go to Network settings, I see two adapters (1 is the local NIC which has a valid IP), the other is my Hyper V Virtual Ethernet adapter with a 169. IP.

                      I have tried giving it a Static but it still wont work!
                      Any assistance would be appreciated. Thanks.

                      Dont know where the issue is but it seems you are getting ip from the internal network. Tey detach the vm.from the switch, destroy it and rebuild it ans reattach it.

                      1 Reply Last reply Reply Quote 0
                      • JoelJ
                        Joel @Jimmy9008
                        last edited by

                        @jimmy9008 said in Hyper-V 2016 (Switch) and NIC:

                        169.x.x.x shouts out that the VM cant reach a DHCP server. If the vSwitch is using the active interface, and allows guest VMs to share the adapter, i'd check if my DHCP server is ok, on the same network, has IPs available etc. The host would be static so thats why that would be working as it was manually configured.

                        Should have thought! A reboot of my router fixed it! Thanks guys.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post