Linux Domain Controller

coliver

Anything in particular you are getting stuck on?

Sparkum

So I believe I followed the link Scott posted fairly well.

I'm trying to do

[root@server1 ~]# firewall-cmd --permanent --zone=public --add-service=samba

to which I just get its not running, reading into it that may be something Cloudatcost is in control of though?

So then even moving past it, I cant seem to browse to it from my house.

I'm using a computer that is currently just pulling DHCP from my router and isnt connected to the domain. Can ping it just fine but cant go \dc (dc is what I made the netbios name)

MattSpeller

@Sparkum said:

So far I think its safe so say I dont have enough Linux knowledge to easily make a linux DC haha

You're doing well so far, stick with it!

coliver

@Sparkum said:

So I believe I followed the link Scott posted fairly well.

I'm trying to do

[root@server1 ~]# firewall-cmd --permanent --zone=public --add-service=samba

to which I just get its not running, reading into it that may be something Cloudatcost is in control of though?

So then even moving past it, I cant seem to browse to it from my house.

I'm using a computer that is currently just pulling DHCP from my router and isnt connected to the domain. Can ping it just fine but cant go \dc (dc is what I made the netbios name)

Nope sounds like the CentOS firewall isn't running. You should turn it on. If I'm not mistaken that may be:

service firewalld start

There may be a different/better way to do it though.

Sparkum

@coliver

Redirecting to /bin/systemctl start firewall.service
Failed to issue method call: Unit firewall.service failed to load: no such file or directory

coliver

@Sparkum said:

@coliver

Redirecting to /bin/systemctl start firewall.service
Failed to issue method call: Unit firewall.service failed to load: no such file or directory

That is interesting. I thought firewalld was installed from scratch on a minimal install. Can you try

yum list installed | grep firewall

That will tell you if that package is installed.

Sparkum

@coliver

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.

coliver

@Sparkum said:

@coliver

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?

Sparkum

@coliver

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

coliver

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

Sparkum

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

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

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.

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?

Sparkum

@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)

You might take a look at Zentyal!

coliver

@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.

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...

Sparkum

@coliver

This means nothing to me haha

coliver

@Sparkum said:

@coliver

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.

scottalanmiller

inet = internet

Internet address is 104.167.119.11/24