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

    Hyper-V VM unable to ping gateway but host can

    Scheduled Pinned Locked Moved IT Discussion
    29 Posts 6 Posters 10.8k Views
    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.
    • wirestyle22W
      wirestyle22 @Dashrender
      last edited by

      @Dashrender said in Hyper-V VM unable to ping gateway but host can:

      @wirestyle22 said in Hyper-V VM unable to ping gateway but host can:

      @dafyre said in Hyper-V VM unable to ping gateway but host can:

      Check and make sure the vSwitch is an external vSwitch.

      Is this the only VM on this host?

      They are using this as a very small file server in addition to the VM but it's the only VM hosted currently.

      Why does it have a static MAC? I know nothing of Hyper-V setups, but that seems odd unless they P2V'ed the VM.

      I had it set to dynamic before, it was just a test.

      1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender
        last edited by

        Have you tried removing the virtual NIC and reinstall it?

        wirestyle22W 1 Reply Last reply Reply Quote 0
        • wirestyle22W
          wirestyle22 @Dashrender
          last edited by wirestyle22

          @Dashrender said in Hyper-V VM unable to ping gateway but host can:

          Have you tried removing the virtual NIC and reinstall it?

          Yes I did. I'm wondering if this has anything to do with the fact that the Dell Poweredge 2900 was one of the first generations to support Hyper-V.

          1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender
            last edited by

            Can you see the vSwitch in the Hyper-V setup itself?

            wirestyle22W 1 Reply Last reply Reply Quote 0
            • wirestyle22W
              wirestyle22 @Dashrender
              last edited by

              @Dashrender You mean in the Virtual Network Manager?

              1 Reply Last reply Reply Quote 0
              • wirestyle22W
                wirestyle22
                last edited by

                This is what I see.
                0_1483453692920_Capture.JPG

                1 Reply Last reply Reply Quote 0
                • wirestyle22W
                  wirestyle22
                  last edited by

                  I really think that this is because the host is 2008 R2 but I don't have enough experience to definitively say that with zero doubt.

                  1 Reply Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender
                    last edited by

                    I'm not sure if Hyper-V 2008 R2 supports a Server 2012 VM or not. that could be the issue.

                    1 Reply Last reply Reply Quote 0
                    • wirestyle22W
                      wirestyle22
                      last edited by wirestyle22

                      Yup. That is the case. https://msdn.microsoft.com/en-us/library/cc794868(v=ws.10).aspx

                      Thanks guys.

                      1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender
                        last edited by

                        Well the good thing is - you can upgrade the hypervisor for free. shut the VM down, copy it somewhere else, wipe the host, reinstall Hyper-V 2016 server, copy the VM back, tada. 🙂

                        wirestyle22W 1 Reply Last reply Reply Quote 2
                        • wirestyle22W
                          wirestyle22 @Dashrender
                          last edited by

                          @Dashrender Yeah that's basically my plan. I'm glad I rad into this. My co-worker tried and I had never attempted to do this before. It's good to know.

                          1 Reply Last reply Reply Quote 0
                          • DashrenderD
                            Dashrender
                            last edited by

                            My bigger question is - why was he deploying a single VM onto a 5 year old hypervisor, when upgrading/installing the latest is free?

                            Oh, I'd skip 2012R2 at this point as well, and go straight to Hyper-V 2016.

                            wirestyle22W 1 Reply Last reply Reply Quote 1
                            • wirestyle22W
                              wirestyle22 @Dashrender
                              last edited by wirestyle22

                              @Dashrender I'm not sure. I think it was for a timeclock so they just wanted something setup quickly. I don't even know if he's the person who did the initial install. We took over for another company and are still finding stuff.--

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