Linux Domain Controller

Sparkum

@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

coliver

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

Sparkum

@coliver

Sorry,

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

coliver

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

Sparkum

@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

Sparkum

@coliver

Sorry never tried this before.

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

coliver

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

Danp

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 firewalld

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

Sparkum

@coliver

State is definitely not running.

Sparkum

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

Sparkum

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

Can access it from windows comp.......No
See it in my domain......No

Sparkum

Here is some of my global and share; I'm assuming this is esentially the most important data

coliver

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

Sparkum

@coliver

Adjusted.

coliver

@Sparkum said:

@coliver

Adjusted.

hosts allow is still going to block anything coming from the public internet. Unless you have a VPN setup between your Samba server and the workstation then you will need to change that to accept the public IP address of the workstation.

Sparkum

@coliver

Oh thats a shame, my ISP doesnt allow dedicated IP's on home networks.

guess I'll have to stay on top of this one.

new ip.JPG

I wonder if I can use one of cloudflare's ip updaters in conjunction with this?

scottalanmiller

That's where a VPN like Pertino is handy.

Dashrender

Did I miss the part where you tried to actually join the SAMBA server to the domain to make it a DC?

As Scott mentioned you'll want to do this over a VPN like Pertino, you definitely don't want to open ports 135, etc to the world on both sides (at C@C and at home) to make this work, which you'd be required to do if you don't use VPN.

Sparkum

@Dashrender

Haha its funny I actually came on here to say "At what point am I prompted to join this to the domain" seemed like all I was doing was making a file share so far.

So to use Pertino for example I would need the VPN on every machine I assume?

I guess my initial plan here is mail server (or SMTP relay even) in the cloud, backup DC (this) in the cloud, dc at home then all my computers and servers, so I would need everything that I want to have access to the cloud DC to have the VPN correct?

Anyone know of any free options for 10-15 computers? (even under 10)

Thanks