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

    Linux Domain Controller

    IT Discussion
    linux debian
    11
    113
    39.7k
    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.
    • C
      coliver @Sparkum
      last edited by coliver

      @Sparkum What about from your workstation/client? I assume it will probably be the same just want to make sure.

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

        Server: google-public-dns-a.google.com
        Address: 8.8.8.8

        Non-authoritative answer:
        Name: dc.pricehouse.ca
        Address: 104.167.119.11

        1 Reply Last reply Reply Quote 0
        • S
          Sparkum @coliver
          last edited by Sparkum

          @coliver

          I'm assuming at one point when I do something "right" this dc should appear in my windows dc like @scottalanmiller mentioned, however; definitely not currently there.

          C 1 Reply Last reply Reply Quote 0
          • C
            coliver @Sparkum
            last edited by coliver

            @Sparkum said:

            @coliver

            I'm assuming at one point when I do something "right" this dc should appear in my windows dc like Scott mentioned, however; definitely not currently there.

            Right, those two IP addresses don't match. Meaning something is wrong with the DNS system. I notice that your workstation is using Google as its primary DNS server. That should be pointing to your DC or on-site DNS server which is authoritative to your zone. Can you ping 10.10.25.10 from your workstation?

            S 1 Reply Last reply Reply Quote 1
            • S
              Sparkum @coliver
              last edited by

              @coliver

              Sorry ignore the initial nslookup that was done at work.

              Second one was done at home, my router is set to point to google.
              Then when I add computers to my domain I change it to my home based DC.

              Should I change the DNS entry to 104.167.119.11 or to my home based 192.168.1.10
              (or both)

              C 1 Reply Last reply Reply Quote 0
              • ?
                A Former User
                last edited by

                You might take a look at Zentyal! 🙂

                C 1 Reply Last reply Reply Quote 0
                • C
                  coliver @A Former User
                  last edited by

                  @Aaron-Studer said:

                  You might take a look at Zentyal! 🙂

                  But then they would miss out on the valuable practice of setting it up themselves.

                  1 Reply Last reply Reply Quote 0
                  • C
                    coliver @Sparkum
                    last edited by coliver

                    @Sparkum said:

                    @coliver

                    Sorry ignore the initial nslookup that was done at work.

                    Second one was done at home, my router is set to point to google.
                    Then when I add computers to my domain I change it to my home based DC.

                    Should I change the DNS entry to 104.167.119.11 or to my home based 192.168.1.10
                    (or both)

                    Can you do

                    ip addr
                    

                    On your Samba server? That should tell you what the public IP address is, compare that to your results... although you really shouldn't be doing LDAP over the public internet... I guess if you were doing LDAPS it wouldn't be so bad but... still...

                    S 1 Reply Last reply Reply Quote 1
                    • S
                      Sparkum @coliver
                      last edited by

                      @coliver

                      centos.PNG

                      This means nothing to me haha

                      C 1 Reply Last reply Reply Quote 0
                      • C
                        coliver @Sparkum
                        last edited by

                        @Sparkum said:

                        @coliver

                        centos.PNG

                        This means nothing to me haha

                        The previous command queries all interfaces on your server. It then pulls the requested info. In this instance we were looking for the IP address. So the lo interface, or local loopback, has the 127.0.0.1 address. Whereas the ens33 interface, or ethernet interface has the ip address of 104.167.119.11. It also shows the IPv6 addresses as well.

                        That IP address matches the one for nslookup so DNS is matching. Although from your home workstation you should use your DC as your primary DNS lookup and Google as the secondary.

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

                          inet = internet

                          Internet address is 104.167.119.11/24

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sparkum @coliver
                            last edited by

                            @coliver

                            So changing home computer to

                            192.168.1.10
                            8.8.8.8

                            I get

                            C:\Users\admin>nslookup dc.pricehouse.ca
                            Server: hostserver.pricehouse.ca
                            Address: 192.168.1.10

                            *** hostserver.pricehouse.ca can't find dc.pricehouse.ca: Non-existent domain

                            so thats interesting

                            C 1 Reply Last reply Reply Quote 0
                            • C
                              coliver @Sparkum
                              last edited by

                              @Sparkum said:

                              @coliver

                              So changing home computer to

                              192.168.1.10
                              8.8.8.8

                              I get

                              C:\Users\admin>nslookup dc.pricehouse.ca
                              Server: hostserver.pricehouse.ca
                              Address: 192.168.1.10

                              *** hostserver.pricehouse.ca can't find dc.pricehouse.ca: Non-existent domain

                              so thats interesting

                              Your hostserver is authoritative for that domain. So you will need to add a DNS entry for it.

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                Sparkum @coliver
                                last edited by

                                @coliver

                                Sorry,

                                A dns entry on my dc to dc.pricehouse.ca?

                                C 1 Reply Last reply Reply Quote 0
                                • C
                                  coliver @Sparkum
                                  last edited by

                                  @Sparkum Right. On the Windows DC, which your workstation is now pointing to, you need to create a A record for the Samba server. That won't fix the issue you are having but you should be able to ping it now.

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    Sparkum @coliver
                                    last edited by

                                    @coliver

                                    Absolutely correct

                                    C:\Users\admin>nslookup dc.pricehouse.ca
                                    Server: hostserver.pricehouse.ca
                                    Address: 192.168.1.10

                                    Name: dc.pricehouse.ca
                                    Address: 104.167.119.11

                                    full pings

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      Sparkum @coliver
                                      last edited by

                                      @coliver

                                      Sorry never tried this before.

                                      My result was forewalld.noarch 0.3.9-11.e.17 @base

                                      C 1 Reply Last reply Reply Quote 0
                                      • C
                                        coliver @Sparkum
                                        last edited by

                                        @Sparkum said:

                                        @coliver

                                        Sorry never tried this before.

                                        My result was forewalld.noarch 0.3.9-11.e.17 @base

                                        So the CentOS firewall is installed, but it won't run, or it is running and dropping traffic. Can you try:

                                        firewall-cmd --state
                                        

                                        It should return running, not running, or command not found.

                                        S 1 Reply Last reply Reply Quote 0
                                        • DanpD
                                          Danp
                                          last edited by

                                          With Centos 7, I believe you should be using "systemctrl" instead of "service".

                                          sudo systemctl enable firewalld
                                          sudo systemctl start firewalld
                                          sudo systemctl status firewalld
                                          ? 1 Reply Last reply Reply Quote 2
                                          • ?
                                            A Former User @Danp
                                            last edited by

                                            @Danp said:

                                            With Centos 7, I believe you should be using "systemctrl" instead of "service".

                                            sudo systemctl enable firewalld
                                            sudo systemctl start firewalld
                                            sudo systemctl status firewalld
                                            

                                            Yep it will redirect the service commands but it's depreciated.

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