NethServer Version: 8
Module: AD
Good day sunshine …
since years we use a Windows-Server with Active Directory (R) as domain controller.
Now we plan to use Nethserver as AD DC - but it’s a big problem to join W10pro to NS-AD. We test this on Proxmox
We have a Firewall (ipfire) that has much options we need. The Firewall offers services: DHCP DNS NTP OVPN …and more.
One virtual machine with Windows10 and one with NS8 (one ethernet card).
NS8 image we loaded down from your website, it’s Rocky-Linux with NS8 basic, because only rocky systems are supported professional and we need support in the future.
We created on NS8 a domain > intern > samba > node1 > (waiting …)
configured all with recommended values: ad.xyz.lan … XYZ … administrator … password … dc1 … win share enabled … static IP of the NS8.
Reboot (an old usualness because of windoooooows)
The W10 v.machine takes his informations from the firewall per dhcp.
NS8 is a known host on the firewall ( ad.xyz.lan IP 172.20.20.246)
W10: Ping ad.xyz.lan gets correct answers from DNS on ipfire.
But if we want to join the domain XYZ windows can’t find the domain !
Where is our missunderstanding ?
btw. we tested other linux SBS (ucs and zentyal) and there was no problem to join with the same machine to the domain … we created snapshot to rollback
It’s not enough to set a DNS A record for the NS8 AD on the firewall. A conditional DNS forward for the AD domain ad.xyz.tld to search the NS8 samba DNS is needed on the firewall.
Alternatively you could set the NS8 as DNS server on the W10 client.
4 Likes
… Thanks,
I thought, I tried this too … set NS8 as 1.DNS server in DHCP options.
Excuse me and
wish a nice weekend
1 Like