Linux Domain Controller
-
Redirecting to /bin/systemctl start firewall.service
Failed to issue method call: Unit firewall.service failed to load: no such file or directory -
@Sparkum said:
Redirecting to /bin/systemctl start firewall.service
Failed to issue method call: Unit firewall.service failed to load: no such file or directoryThat is interesting. I thought firewalld was installed from scratch on a minimal install. Can you try
yum list installed | grep firewallThat will tell you if that package is installed.
-
Correct me if I'm wrong though but I assume I have more than one issue.
I cant browse to \dc but if the firewall is off that means thats not preventing me from accessing it, so there's another reason for that particular problem, and just a second one with the firewall.
-
@Sparkum said:
Correct me if I'm wrong though but I assume I have more than one issue.
I cant browse to \dc but if the firewall is off that means thats not preventing me from accessing it, so there's another reason for that particular problem, and just a second one with the firewall.
I would assume you need to use the Fully Qualified Domain Name, did you point an address to that dc? What happens if you do nslookup dc from your client? Oh you said you can ping it, is that by the netbios name?
-
Changed netbios name to dc.pricehouse.ca
10.25.10.10.in-addr.arpa
primary name server = localhost
responsible mail addr = nobody.invalid
serial = 1
refresh = 600 (10 mins)
retry = 1200 (20 mins)
expire = 604800 (7 days)
default TTL = 10800 (3 hours)
Server: UnKnown
Address: 10.10.25.10 -
@Sparkum What about from your workstation/client? I assume it will probably be the same just want to make sure.
-
Server: google-public-dns-a.google.com
Address: 8.8.8.8Non-authoritative answer:
Name: dc.pricehouse.ca
Address: 104.167.119.11 -
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.
