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

    Additional AD Issue

    IT Discussion
    4
    40
    5.0k
    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.
    • G
      Ghani @Dashrender
      last edited by

      @Dashrender

      192.168.1.124 of AD server
      192.168.1.124 of DNS server [ Note : Only on DNS server ].
      192.168.1.125 { it is ip address of new AD server ]

      Thanks

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

        @Dashrender

        OP means ?

        S 1 Reply Last reply Reply Quote 0
        • S
          scottalanmiller @Ghani
          last edited by

          @Ghani said in Additional AD Issue:

          @Dashrender

          OP means ?

          Original Poster

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

            @Ghani said in Additional AD Issue:

            @Dashrender

            192.168.1.124 of AD server
            192.168.1.124 of DNS server [ Note : Only on DNS server ].
            192.168.1.125 { it is ip address of new AD server ]

            Thanks

            what kind of switch is in use? are both servers plugged into the same switch?

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

              Is the first AD server a VM? is this new desired AD server a VM? you might have posted already, but I'm tired, and not back reading 🙂

              G 1 Reply Last reply Reply Quote 0
              • G
                Ghani @Dashrender
                last edited by

                @Dashrender

                Yes . new AD is a virtual machine running on VMware hypervisor.

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

                  @Ghani said in Additional AD Issue:

                  @Dashrender

                  Yes . new AD is a virtual machine running on VMware hypervisor.

                  What version? Is there a firewall inside ESXi? and network level blocking going on?

                  G 1 Reply Last reply Reply Quote 0
                  • G
                    Ghani @Dashrender
                    last edited by

                    @Dashrender

                    Existing AD running on physical server. New Additional domain controller machine running on virtual machine.

                    1 Reply Last reply Reply Quote 0
                    • G
                      Ghani @Dashrender
                      last edited by

                      @Dashrender

                      how to check any firewall or network level block on VMware hypervison ?

                      G 1 Reply Last reply Reply Quote 0
                      • G
                        Ghani @Ghani
                        last edited by

                        @Ghani

                        VMware Hypervisor version 6.0 update 2

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

                          can you ping the original AD from the VM by FQDN? (fully qualified domain name)

                          G 1 Reply Last reply Reply Quote 0
                          • G
                            Ghani
                            last edited by

                            I facing error screen shot attached here 0_1483073437522_Error1.PNG 0_1483073455139_Error2.PNG

                            kindly provide any solution for creating Additional domain controller.

                            1 Reply Last reply Reply Quote 0
                            • G
                              Ghani @Dashrender
                              last edited by

                              @Dashrender

                              Yes i could pinging the FQDN name.

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

                                did you do as it said and remove this server from the domain, reboot, and readd it?

                                G 1 Reply Last reply Reply Quote 0
                                • G
                                  Ghani @Dashrender
                                  last edited by

                                  @Dashrender

                                  yaa i checked

                                  1 Reply Last reply Reply Quote 0
                                  • G
                                    Ghani
                                    last edited by

                                    I got event error from new Additional DC

                                    1_1483084293365_jp2.PNG 0_1483084293363_jp1.PNG

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

                                      Please show pictures of your IP settings on both the original AD and the new VM.

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

                                        This error is sounding like you have DNS installed on the new AD server already, but that it's misconfigured. Open the DNS applet and do what this error says, check to see if DNS is running on the IP address that is currently assigned to the server. Perhaps the server came online and got a DHCP address, they you installed DNS, so it tied to that IP, then you set IP to a manual setting which is different from the selected one in DNS. This does seem weird that this would happen, but hey, stranger things, eh?

                                        https://i.imgur.com/0JX0bcT.png

                                        Check your DNS manager settings on both servers
                                        https://i.imgur.com/KlphvDp.png

                                        Also, This error message leads me to think that this new AD box might be pointing to itself for DNS, instead of pointing to the other AD server for DNS.

                                        Please post pictures of the IP settings on both servers.

                                        G 1 Reply Last reply Reply Quote 0
                                        • G
                                          Ghani @Dashrender
                                          last edited by

                                          @Dashrender

                                          OK , i will check it

                                          G 1 Reply Last reply Reply Quote 0
                                          • G
                                            Ghani @Ghani
                                            last edited by

                                            @Ghani

                                            All ready check the All IP address interface on existing domain controller dns server

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