m.traeumner
(Michael Träumner)
March 12, 2018, 9:33am
4
Did you try to ping your Win 10 with the IP or the hostname? Also you may have a look at the Win 10 firewall, if ping is blocked.
Please have a look at this post too:
@Mario_Lanno
I was also experiencing problems joining WIn 10 client to our NT4-style domain.
My domain name was JIMBO.COM .
I succesfully joined Win XP an Win 7 clients, no chance with Win 10.
After applying the registry patch without unnecessary values, I renamed my domain from JIMBO.COM to JIMBO-DC (according to Nethserver Admin Guide ).
Once modified the domain name, I’ve been able to enlist my Win 10 client into JIMBO-DC.
This is the patch applied:
Windows Registry Editor Version 5.00
…
and here:
docs.nethserver.org/projects/nethserver-devel/en/v7/nethserver-dc.html
/var/lib/nethserver/ibay
is the location.Better not to change it, because of the backup.
If you want to have another location you can mount the other location to the /var/lib/nethserver/ibay folder.
NethServer Version: 7.3 RC3
Module: Domain Controller, shares
Folks, seeing some good things on 7 RC3 (with a few reservation the wizard and sssd.conf file being deleted upon creation of a domain). One thing that would awesome and I’m trying to do manually, is to map the Samba default shares given to newly created profiles as well as group (or LDAP) share mapped to an external NAS. (Freenas to be exact). there are reasons for this. Storage space being the biggie. I have a fstab entry to auto…
2 Likes