NethServer Version: NethServer release 7.6.1810 (final)
I’m looking for the proper setup that allows proper communication to the Active Directory Domain Controller container from a different subnet outside of the one that was initially configured and setup during initial container setup process.
All is well on basic setup and config for our main LAN subnet (able to join a windows machine that sits on the same /16 subnet as the Nethserver DC) The issue is our WLAN subnet is it’s own separate /16 subnet.
Example subnet info (not exact ones used on LAN)
nethserver vm: 10.20.1.253
NSDC container: 10.20.1.252
br0 was auto configured for the container when it was initially turned on/created.
A little background on a similar situation - We currently have a Zentyal DC running on this same network where we added a 2nd NIC to that vm for the WLAN subnet. Then we simply adjusted which IP to use on a given device for what it uses as DNS to point to the matching interface 10.20.x.x for LAN machines, 10.25.x.x for wireless machines.
(Side Discussion here while I’m at it. Do we point client machines to the Nethserver Host IP or the NSDC container IP for DNS before joining to domain? I noticed using either worked for the LAN machine that joined OK.)
I attempted to do this on NS by adding another NIC to the VM, configuring it in network tab in GUI. I can ping the additional IP now but not sure what needs to be done on the bridge side of this or additional config on the container side if any to allow the needed traffic over this additional IP when a machine attempts to join the domain using the additional NIC as it’s DNS.
Error received during the domain join attempt on a PC on the WLAN subnet. Taken from c:\WINDOWS\debug\dcdiag.txt
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain “ccs.com”:
The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs.com
The following domain controllers were identified by the query:
However no domain controllers could be contacted.
Common causes of this error include:
Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.
Domain controllers registered in DNS are not connected to the network or are not running.
nsdc-nethserver.ccs.com is the proper name of the NSDC container here but it appears as though the request doesnt make it to the container?
Any pointers or help on this is greatly appreciated. I also spent a decent amount of time searching for old posts on this topic but did not have much luck to this point.