> Dewayne, > > I would never have posted the message if my DNS was not functional. Here > are the answers (on the AD server and on the S3 server) for the tests of > the HOWTO : > > > host -t SRV _ldap._tcp.sc.isc84.org. > _ldap._tcp.sc.isc84.org has SRV record 0 100 389 vspdc.sc.isc84.org. > > > host -t SRV _kerberos._udp.sc.isc84.org. > _kerberos._udp.sc.isc84.org has SRV record 0 100 88 vspdc.sc.isc84.org. > > > host -t A vspdc.sc.isc84.org. > vspdc.sc.isc84.org has address 192.168.77.1 > > All seems good unless I have missed something. The problem is when I > join my S3 in the AD (kerberos is functionnal) > > net join -Uadministrateur > *Using short domain name -- SC > Joined 'SSC011' to realm 'sc.isc84.org'* > /*DNS Update for ssc011.sc.isc84.org failed: > ERROR_DNS_INVALID_MESSAGE DNS update failed!*/ > > The join seems to have worked in spite of the error message concerning > the DNS. And in a windows box \\ssc011 does not work. But I don't know > if these problems are bounded. >
>>> >>> I've followed the document and i can see in the AD the server >>> included. >>> But I've the following error when doing the following command : >>> >>> > net join -Uadministrateur >>> Using short domain name -- SC >>> Joined 'SSC011' to realm 'sc.isc84.org' >>> *DNS Update for ssc011.sc.isc84.org failed: >>> ERROR_DNS_INVALID_MESSAGE DNS update failed!* >>> >>> Moreover I can't access from a window box to my server with >>> \\ssc011 (the name of my server). >>> >>> My /ets/hosts >>> >>> 127.0.0.1 ssc011.sc.isc84.org ssc011 localhost >>> 192.168.77.4 ssc011.sc.isc84.org ssc011 >>> 192.168.77.1 vspdc.sc.isc84.org vspdc >>> >>> "sc" is the samba3 domain >>> 192.168.77.1 -> is the samba4 PDC >>> 192.168.77.4 -> is the samba 3.6 file server which has the >>> name "ssc011" >>> >>>>> Hello >>>>> >>>>> How to set a S3 file server as a domain member with a S4 >>>>> >>> PDC server ? >>> >>>>> >>>>> >>>> You can join Samba 3.x or Samba 4.0 as a domain member of a >>>> >>> Samba 4.0 >>> >>>> AD DC in the same way you would join any other AD domain. >>>> >>> eg 'net ads >>> >>>> join. >>>> >>>> See >>>> >>>> >>> https://www.samba.org/samba/docs/man/Samba-Guide/unixclients.html#adss >>> >>>> dm >>>> >>>> >>>> >>> -- >>> >>> Hervé Hénoch >>> Responsable informatique >>> Institut Sainte Catherine >>> 250 chemin de Baigne-Pieds >>> CS 80005 --- 84918 AVIGNON cedex 9 >>> Téléphone : 04.90.27.57.44 >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba >>> >>> >> Herve, >> Samba4 provides a lot of features though it does have some >> prerequisites; please review the HowTo, and particularly >> https://wiki.samba.org/index.php/Samba4/HOWTO#Step_7:_Configure_DNS >> noting the first line "A working DNS setup is essential to the >> correct operation of Samba." >> >> It's a hard road (if you're not familiar with being a Windows Admin) but >> well worth the effort. >> Regards, Dewayne. >> I think you should use net ads join -U Administrator%password to join to an AD domain. Felix. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba