search for: modianodc

...read: https://lists.samba.org/archive/samba/2016-April/thread.html#199609 Maybe I misunderstood the solution and I changed only the mapping in winbind. Is that so? >From the AD DC: > smb.conf # Global parameters [global] bind interfaces only = Yes interfaces = lo ens32:SMB netbios name = MODIANODC realm = MODIANOAD.MODIANO.COM workgroup = MODIANOAD dns forwarder = 192.168.100.5 server role = active directory domain controller idmap_ldb:use rfc2307 = yes comment = "TEST AD" log level = 4 log file = /var/log/samba/log.samba password hash gpg key ids = XXXXXXXXX # Needed t...

...test1 > > > /etc/hosts > 127.0.0.1 localhost > # The following lines are desirable for IPv6 capable hosts > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > 192.168.100.50 sambatest1.modiano.com sambatest1 > 192.168.100.51 MODIANODC.modianoad.modiano.com MODIANODC > > Bit confused here (not hard) ;-) I take it the above three files are from the DC and the netbios name is 'MODIANODC' yet /etc/hostname contains 'sambatest1' If this is the DC, you don't need '192.168.100.50 sambatest1.modiano.com...

Hi, we are testing a new AD domain that will replace our old NT4 one, and we are setting up a new cifs vserver of our Netapp filer (running Clustered Dataontap 9.2). The new AD domain was a clean deployment created using "samba-tool domain provision --server-role=dc --use-rfc2307 ...". All seems to work well and the Netapp filer joins the domain without errors and seems to run fine.