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.
    • D
      Dashrender @scottalanmiller
      last edited by

      @scottalanmiller said in Additional AD Issue:

      Almost certainly DNS. Can you ping the server(s)?

      Pinging isn't 100% reliable way to know DNS is setup correctly - Windows will use other methods to find each other, then move over to IP to complete the ping.

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

        @Dashrender said in Additional AD Issue:

        @scottalanmiller said in Additional AD Issue:

        Almost certainly DNS. Can you ping the server(s)?

        Pinging isn't 100% reliable way to know DNS is setup correctly - Windows will use other methods to find each other, then move over to IP to complete the ping.

        No, but we need to know if it is pingable at all.

        1 Reply Last reply Reply Quote 0
        • R
          RoopanKumar
          last edited by

          NO issue with dns, but if we join in domain the dns record is not created in forward lookup we are creating manually.

          pinging was successful no problem with that @scottalanmiller @Dashrender

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

            Oh. It is joining okay just not making a record? There is a checkbox for that.

            R 1 Reply Last reply Reply Quote 0
            • R
              RoopanKumar @scottalanmiller
              last edited by

              @scottalanmiller said in Additional AD Issue:

              Oh. It is joining okay just not making a record? There is a checkbox for that.

              what kind of checkbox you are asking for

              1 Reply Last reply Reply Quote 0
              • R
                RoopanKumar
                last edited by

                unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)

                unable to telnet port like 88 (from adc new to ad old )

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

                  @RoopanKumar said in Additional AD Issue:

                  unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)

                  unable to telnet port like 88 (from adc new to ad old )

                  Why are you trying to telnet?

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

                    What is the IP address of your current AD server?
                    What is the IP address of your DNS server? Do you have more than one DNS server?
                    What is the IP address of the server you are trying to install AD onto?

                    R D 2 Replies Last reply Reply Quote 0
                    • R
                      RoopanKumar @Dashrender
                      last edited by

                      @Dashrender this is for my team mate ask this boy @Ghani

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

                        Yes, we are using telnet to establish session from new windows server OS to existing Domain controller. The ports [ 389,3268,3269,464,53] are establised session, except port 88. And then , we using telnet to establish session from
                        existing domain controller to new windows server OS that time , the ports [ 389,3268,3269,464,88] are not established session in between existing DC and windows server. Only 53 and 445 ports are establish the session. But i am using netstat -n commands on existing DC. 389,3268,3269,464,53,88 ports are open.

                        Thanks
                        Ghani

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

                          @Dashrender said in Additional AD Issue:

                          What is the IP address of your current AD server?
                          What is the IP address of your DNS server? Do you have more than one DNS server?
                          What is the IP address of the server you are trying to install AD onto?

                          @Ghani what are the answers to these questions?

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

                            @Dashrender said in Additional AD Issue:

                            @RoopanKumar said in Additional AD Issue:

                            unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)

                            unable to telnet port like 88 (from adc new to ad old )

                            Why are you trying to telnet?

                            That's how you test ports

                            R D 2 Replies Last reply Reply Quote 0
                            • R
                              RoopanKumar @scottalanmiller
                              last edited by

                              @scottalanmiller yeah is there any other option to check ports

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

                                @scottalanmiller said in Additional AD Issue:

                                @Dashrender said in Additional AD Issue:

                                @RoopanKumar said in Additional AD Issue:

                                unable to telnet port like 88, 389, 3268, 3269, 464 (from ad old to adc new)

                                unable to telnet port like 88 (from adc new to ad old )

                                Why are you trying to telnet?

                                That's how you test ports

                                Yeah OK.. what do these ports have to do with the OP issue?

                                G 1 Reply Last reply Reply Quote 0
                                • 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
                                            • 1
                                            • 2
                                            • 2 / 2
                                            • First post
                                              Last post