NethServer Version: 8Module: SAMBA AD
Having an issue with a newly created AD DC on Nethserver 8. I’m running in VMware, with NAT networking. I cannot seem to connect to the domain.
When I put the nethserver’s vm’s IP for DNS, the windows computer loses access to the internet and cannot find the domain.
Info:
Nethserver 8 running on AlmaLinux 9.8 - static IP of 192.168.153.140
Domain: ad.limesvc.lan, set up through domains and users workflow.
Does anyone have any possible insights or see anything obvious I’ve missed? Thanks!
Screen shot from Win 11 VM
mrmarkuz
July 27, 2026, 7:17pm
3
Hi John,
welcome to NethServer Community.
It seems that you didn’t enable the Samba file server. In this case Samba uses the Wireguard VPN IP (10.5.4.1) instead of the LAN one so the clients can’t join the domain and the Samba DNS is unreachable.
After changing the Samba IP, the Samba DC should be reachable for clients:
Hi,
please disable the DNSmasq DNS first because it conflicts with Samba on the same node as both want to use the same ports.
it seems you didn’t enable the file server (which includes authentication, see User domains | NethServer 8 documentation ) as the Samba server has a wireguard VPN IP 10.5.4.1 which isn’t reachable from LAN.
I assume there’s just one NS8 node and a single samba server without replicas. In this case it’s possible to change the IP to the LAN one - 192.168.16.7:
api-cli ru…
Thank you! That fixed it!
