Linux Domain Controller
-
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.
-
@Sparkum said:
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?
-
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) -
You might take a look at Zentyal!
-
@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.
-
@Sparkum said:
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 addrOn 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...
-
-
@Sparkum said:
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.
-
inet = internet
Internet address is 104.167.119.11/24
-
So changing home computer to
192.168.1.10
8.8.8.8I 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
-
@Sparkum said:
So changing home computer to
192.168.1.10
8.8.8.8I 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.
-
-
@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.
-
Absolutely correct
C:\Users\admin>nslookup dc.pricehouse.ca
Server: hostserver.pricehouse.ca
Address: 192.168.1.10Name: dc.pricehouse.ca
Address: 104.167.119.11full pings
-
-
-
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 -
@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 firewalldYep it will redirect the service commands but it's depreciated.
-
State is definitely not running.
-
Well for some reason when I got home and started to re-try everything after confirming the service was indeed stopped, suddenly I could start it, and complete step 8 with success....
Still not a DC but progress for sure
