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

    Domain Controller Down (VM)

    IT Discussion
    16
    609
    96.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.
    • D
      Dashrender
      last edited by

      log into the 2008 DC and look at it's IP settings and share them if possible.

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

        @Dashrender

        192.168.10.55
        255.255.255.0
        192.168.10.1

        1 Reply Last reply Reply Quote 0
        • D
          DustinB3403 @Dashrender
          last edited by

          @Dashrender said in Domain Controller Down (VM):

          @DustinB3403 said in Domain Controller Down (VM):

          @JaredBusch said in Domain Controller Down (VM):

          @DustinB3403 said in Domain Controller Down (VM):

          @wirestyle22 said in Domain Controller Down (VM):

          @JaredBusch said in Domain Controller Down (VM):

          @wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.

          Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).

          This host DNS is set to using the VM that is offline.

          The fact that this VM is offline is the cause of the DNS related issues he's having.

          Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.

          Fair enough, I was looking at the problem of him not being able to access the host from vsphere.

          But it's a trivial issue.

          he's not trying to connect to vsphere via a hostname though, he's trying to use an IP address.

          He was also using the wrong IP address. In either case it means that there is nothing wrong with the equipment between the hypervisor and his workstation (or the rest of the network).

          I think I read this already, but is it not possible to restore a backup of this VM. (are there none?)

          J 1 Reply Last reply Reply Quote 0
          • D
            Dashrender
            last edited by

            can you log into the vSphere web console?

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

              @Dashrender said in Domain Controller Down (VM):

              can you log into the vSphere web console?

              No

              D D 2 Replies Last reply Reply Quote 0
              • J
                JaredBusch @DustinB3403
                last edited by

                @DustinB3403 said in Domain Controller Down (VM):

                @Dashrender said in Domain Controller Down (VM):

                @DustinB3403 said in Domain Controller Down (VM):

                @JaredBusch said in Domain Controller Down (VM):

                @DustinB3403 said in Domain Controller Down (VM):

                @wirestyle22 said in Domain Controller Down (VM):

                @JaredBusch said in Domain Controller Down (VM):

                @wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.

                Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).

                This host DNS is set to using the VM that is offline.

                The fact that this VM is offline is the cause of the DNS related issues he's having.

                Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.

                Fair enough, I was looking at the problem of him not being able to access the host from vsphere.

                But it's a trivial issue.

                he's not trying to connect to vsphere via a hostname though, he's trying to use an IP address.

                He was also using the wrong IP address. In either case it means that there is nothing wrong with the equipment between the hypervisor and his workstation (or the rest of the network).

                I think I read this already, but is it not possible to restore a backup of this VM. (are there none?)

                None known. At this point we are simply trying to get the VMDK to recreate the VM

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

                  @wirestyle22 said in Domain Controller Down (VM):

                  @Dashrender said in Domain Controller Down (VM):

                  can you log into the vSphere web console?

                  No

                  What is the IP of that?

                  is the ESXi server with the down VM on it 192.168.10.14?
                  I'm trying to keep that stuff straight as I help.

                  1 Reply Last reply Reply Quote 0
                  • W
                    wirestyle22 @JaredBusch
                    last edited by

                    @JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant

                    D 1 Reply Last reply Reply Quote 0
                    • D
                      DustinB3403 @wirestyle22
                      last edited by

                      @wirestyle22 said in Domain Controller Down (VM):

                      @Dashrender said in Domain Controller Down (VM):

                      can you log into the vSphere web console?

                      No

                      How are you trying to access the Web console, via IP in a web browser or by a URL?

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

                        @wirestyle22 said in Domain Controller Down (VM):

                        @JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant

                        when pinging what?

                        J W 2 Replies Last reply Reply Quote 0
                        • J
                          JaredBusch @Dashrender
                          last edited by

                          @Dashrender said in Domain Controller Down (VM):

                          @wirestyle22 said in Domain Controller Down (VM):

                          @JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant

                          when pinging what?

                          I did not think ping doe not resolved hostname on ESXi. What exactly are you doing?

                          1 Reply Last reply Reply Quote 0
                          • D
                            Dashrender @DustinB3403
                            last edited by

                            @DustinB3403 said in Domain Controller Down (VM):

                            @wirestyle22 said in Domain Controller Down (VM):

                            @Dashrender said in Domain Controller Down (VM):

                            can you log into the vSphere web console?

                            No

                            How are you trying to access the Web console, via IP in a web browser or by a URL?

                            good point.

                            try
                            https://ip address:9443/vsphere-client/

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

                              @Dashrender said in Domain Controller Down (VM):

                              @wirestyle22 said in Domain Controller Down (VM):

                              @JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant

                              when pinging what?

                              There is a network test in ESXi that pings 3 IP addresses. 1 is the gateway. 2 is the 2003 DC which isnt on, 3 is the 2008 DC and 4 is the hostname. the 2008 DC is the only successful now although the first test the hostname did resolve. It has not since.

                              D 1 Reply Last reply Reply Quote 0
                              • D
                                DustinB3403 @wirestyle22
                                last edited by

                                @wirestyle22 said in Domain Controller Down (VM):

                                @Dashrender said in Domain Controller Down (VM):

                                @wirestyle22 said in Domain Controller Down (VM):

                                @JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant

                                when pinging what?

                                There is a network test in ESXi that pings 3 IP addresses. 1 is the gateway. 2 is the 2003 DC which isnt on, 3 is the 2008 DC and 4 is the hostname. the 2008 DC is the only successful now although the first test the hostname did resolve.

                                You're having DNS issues, so it's expected that DNS would fail eventually.

                                How are you trying to access the Web Console?

                                Are you using https://SERVER-NAME:9443/vsphere-client/ or https://ip address:9443/vsphere-client/

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

                                  Not being able to ping the gateway means it sounds like something was restricted on the management network.

                                  Since your 2003 DC is down, give your workstation the IP of the DC and try to connect with the thick client.

                                  D W 2 Replies Last reply Reply Quote 0
                                  • D
                                    Dashrender @JaredBusch
                                    last edited by

                                    @JaredBusch said in Domain Controller Down (VM):

                                    Not being able to ping the gateway means it sounds like something was restricted on the management network.

                                    Since your 2003 DC is down, give your workstation the IP of the DC and try to connect with the thick client.

                                    Would you be able to see those restrictions in the DOS-like interface on the server console?

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

                                      @DustinB3403 said in Domain Controller Down (VM):

                                      @wirestyle22 said in Domain Controller Down (VM):

                                      @Dashrender said in Domain Controller Down (VM):

                                      @wirestyle22 said in Domain Controller Down (VM):

                                      @JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant

                                      when pinging what?

                                      There is a network test in ESXi that pings 3 IP addresses. 1 is the gateway. 2 is the 2003 DC which isnt on, 3 is the 2008 DC and 4 is the hostname. the 2008 DC is the only successful now although the first test the hostname did resolve.

                                      You're having DNS issues, so it's expected that DNS would fail eventually.

                                      How are you trying to access the Web Console?

                                      Are you using https://SERVER-NAME:9443/vsphere-client/ or https://ip address:9443/vsphere-client/

                                      I specifically have him not using the web client to avoid DNS issues. 5.1 was still fully dependant on the thick client as well. It was 5.5 i think when feature started not being available in the thick client.

                                      D 1 Reply Last reply Reply Quote 2
                                      • J
                                        JaredBusch @Dashrender
                                        last edited by JaredBusch

                                        @Dashrender said in Domain Controller Down (VM):

                                        @JaredBusch said in Domain Controller Down (VM):

                                        Not being able to ping the gateway means it sounds like something was restricted on the management network.

                                        Since your 2003 DC is down, give your workstation the IP of the DC and try to connect with the thick client.

                                        Would you be able to see those restrictions in the DOS-like interface on the server console?

                                        Been too long since I had a live system. I cannot tell you.

                                        1 Reply Last reply Reply Quote 0
                                        • StrongBadS
                                          StrongBad
                                          last edited by

                                          Seems like avoiding anything but IP addresses and direct access is best. Just too many things going wrong.

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

                                            @JaredBusch said in Domain Controller Down (VM):

                                            @DustinB3403 said in Domain Controller Down (VM):

                                            @wirestyle22 said in Domain Controller Down (VM):

                                            @Dashrender said in Domain Controller Down (VM):

                                            @wirestyle22 said in Domain Controller Down (VM):

                                            @JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant

                                            when pinging what?

                                            There is a network test in ESXi that pings 3 IP addresses. 1 is the gateway. 2 is the 2003 DC which isnt on, 3 is the 2008 DC and 4 is the hostname. the 2008 DC is the only successful now although the first test the hostname did resolve.

                                            You're having DNS issues, so it's expected that DNS would fail eventually.

                                            How are you trying to access the Web Console?

                                            Are you using https://SERVER-NAME:9443/vsphere-client/ or https://ip address:9443/vsphere-client/

                                            I specifically have him not using the web client to avoid DNS issues. 5.1 was still fully dependant on the thick client as well. It was 5.5 i think when feature started not being available in the thick client.

                                            Ah I missed that you had him download the management client.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 30
                                            • 31
                                            • 3 / 31
                                            • First post
                                              Last post