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

    Hyper-V Was working, now it isnt

    IT Discussion
    hyper-v
    4
    14
    1.8k
    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.
    • popesterP
      popester
      last edited by scottalanmiller

      No matter what I do I keep getting the same issue. When trying to connect from my management server to the headless HOST I get the following.
      0_1521491435528_Screen Shot 2018-03-19 at 3.05.16 PM.png

      This is the Host Machine.

      0_1521491566020_Screen Shot 2018-03-19 at 3.31.50 PM.png

      This is the management machine which is a VM.

      0_1521491661808_Screen Shot 2018-03-19 at 3.33.41 PM.png

      I keep going around in circles from everything I have googled. I did enable a virtual nic card which knocked me out and then i could not connect anymore. I was able to remove the vitual interface which caused the box to go back to the physical NIC. I reestablished connectivity to the box and can RDP into it. I can ping each box from one to the other. This tells me I am back on the network and everything is talking except I keep getting the WinRM cannot complete the operation. I am fully prepared to take the lumps due if it is something simple like "have you rebooted". (I have) I have really tried to get this one figured out but lack of experience is eating my lunch. Any pointers would greatly be appreciated.

      Manager pinging host:

      0_1521492334180_Screen Shot 2018-03-19 at 3.43.43 PM.png

      Host pinging Manager:

      0_1521492428242_Screen Shot 2018-03-19 at 3.46.21 PM.png

      Apologies if this format is bad. Pointers on that would be good too. Thank you.

      1 Reply Last reply Reply Quote 3
      • DustinB3403D
        DustinB3403
        last edited by

        Have you attempted to connect to this server using it's IP address rather than its FQDN?

        popesterP 1 Reply Last reply Reply Quote 0
        • DustinB3403D
          DustinB3403
          last edited by

          Also have you confirmed the settings in the firewall.

          0_1521492950221_chrome_2018-03-19_16-54-45.png

          popesterP 1 Reply Last reply Reply Quote 0
          • popesterP
            popester @DustinB3403
            last edited by

            @dustinb3403 said in Hyper-V Was working, now it isnt:

            Have you attempted to connect to this server using it's IP address rather than its FQDN?

            Different error:

            0_1521493062214_Screen Shot 2018-03-19 at 3.57.20 PM.png

            1 Reply Last reply Reply Quote 0
            • popesterP
              popester @DustinB3403
              last edited by

              @dustinb3403 working on that now.

              1 Reply Last reply Reply Quote 0
              • DustinB3403D
                DustinB3403
                last edited by

                Based on the above information and the error code I called out, I'd take a look at the firewall settings and see if there is something off there.

                IE: Due to what the error is saying, you aren't being allowed access purely due to being on a different sub

                popesterP 1 Reply Last reply Reply Quote 1
                • popesterP
                  popester @DustinB3403
                  last edited by

                  @dustinb3403 said in Hyper-V Was working, now it isnt:

                  Based on the above information and the error code I called out, I'd take a look at the firewall settings and see if there is something off there.

                  IE: Due to what the error is saying, you aren't being allowed access purely due to being on a different sub

                  Thats a great point. They are, on different subnets. Gotta get better at reading the error message. Thanks man!! Will follow up if i get is working.

                  DustinB3403D 1 Reply Last reply Reply Quote 1
                  • DustinB3403D
                    DustinB3403 @popester
                    last edited by

                    @popester I hope it works out.

                    Keep us informed.

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

                      I have a domain joined Hyper-V setup that the Win 10 desktop running Hyper-V manager has to have the firewall turned off to connect.

                      No issues on the Hyper-V Server 2012 R2 side.

                      Have not had time to troubleshoot yet. Just discovered it the other weekend when I was on site at a client.

                      DustinB3403D 1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403 @JaredBusch
                        last edited by

                        @jaredbusch Are the server and workstation on the same subnet?

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

                          @dustinb3403 said in Hyper-V Was working, now it isnt:

                          @jaredbusch Are the server and workstation on the same subnet?

                          In my case? Yes. Both domain joined also. Issue started within the last month or so.

                          DustinB3403D 1 Reply Last reply Reply Quote 0
                          • DustinB3403D
                            DustinB3403 @JaredBusch
                            last edited by

                            @jaredbusch So likely not the same issue.

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

                              Another tech I know found that he could not manage non domain joined Hyper-V hosts from a different subnet. Not sure he ever got around that issue.

                              1 Reply Last reply Reply Quote 0
                              • popesterP
                                popester
                                last edited by

                                I ended up starting over from bare metal. Second attempt was A LOT better. Thank you everyone for all of your help.

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