Linux Domain Controller
-
@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
-
So at this point I would have to assume that there is a mistake in on smb.conf file eh?
Just going through the checklist
Installed samba ....... Yep
smb.conf file .........Prob?
Made samba/anonymous.....yep
Firewall steps........yepCan access it from windows comp.......No
See it in my domain......No -
Here is some of my global and share; I'm assuming this is esentially the most important data
-
@Sparkum said:
Here is some of my global and share; I'm assuming this is esentially the most important data
I don't think you have an eth0 interface. At least not from the previous screenshot. I believe your interface is called ens33. Although I could be mistaken. Also your hosts allow option isn't going to let your workstation connect to it as it isn't in one of those subnets.
-
Adjusted.
-
