Wanting to throw out Zentyal, I downloaded and installed nethserver 7.2 RC2. Running as a VM under VirtualBox on Linux Mint 17.I have only one NIC defined. Unattended installation went fine, and all basic LAN settings configured. All patches and updates ran fine. In software centre I installed: Account Provider Samba Active Directory, Backup, Basic Firewall, File Server.
I created a share called test (test share) DNS and DHCP seem to be running fine, dhcp clients can resolve hostnames on LAN, and Internet access is fine from server and clients.
Nethserver is nethserver.mydomain.lan IP 192.168.22.6.
nsdc-nethserver.mydomain.lan exists, IP 192.168.22.7.
client can successfully ping both nethserver and nethserver.mydomain.lan.
Pinging nsdc-nethserver.mydomain.lan, resolves to 192.168.22.7, but no reply.
I am unable to access 192.168.22.7 using ssh on port 2222 or 22.
Joining a Windows 7 client to mydomain.lan, reports failed. The lookup returned the correct hostname nsdc-nethserver.mydomain.lan, but says cannot be contacted, or no response.
Is there a special firewall rule that has to be made to allow access to /from nsdc-nethserver?
The share is visible.
Also, strange that NS is the Primary and only DEC for my AD domain, I would have expected to see some existing user groups in the list, such as administrators, domain admins, something. The only ones are ones I created. User sdministrator is there, but belongs to no groups?