search for: kinaxia

Displaying 9 results from an estimated 9 matches for "kinaxia".

Did you mean: binaria
2016 Jun 07
2
Samba AD member lost domain join after reboot
I put the usermapping but this does not solve the problem. I do not use libpam_winbind and libpam-krb5 because I did not need to log in server using domain accounts, it seems to me that this is not mandatory, you confirm ? Here are the permissions of the file /etc/krb5.keytab: root at smb1:/home/adminlocal# ls -l /etc/krb5.keytab -rw------- 1 root root 2312 Jun 7 14:44 /etc/krb5.keytab Avahi
2016 Jun 07
6
Samba AD member lost domain join after reboot
...works for me: > > root at debnet:/home/rowland/ # wbinfo -P > checking the NETLOGON dc connection to "dc1.samdom.example.com" succeeded > > Rowland > > > > -- k Alexis RIES Service informatique Tel : 04.22.32.97.26 Fax : 04.84.25.27.40 Email : alexis.ries at kinaxia.fr http://www.kinaxia.fr -------------- next part -------------- Nom Type Données Horodateur _sites _tcp _udp DomainDnsZones ForestDnsZones (identique au dossier parent) Source de nom (SOA) [43], dc1.ad.samdom.local., hostmaster.ad.samdom.local. ?07/?06/?2016 17:00:00 (identique a...
2016 Jun 06
2
Samba AD member lost domain join after reboot
Hello, After each reboot, my Samba AD member server lost domain join after reboot, I have to re-enter the server in the domain with the "net ads join -U administrator". I use version 4.4.3 of samba. The domain controller is a Samba AD server. After reboot, when I exectute "net ads testjoin" I have: kerberos_kinit_password SMB2$@AD.SAMDOM.LOCAL failed: failed
2016 Jun 07
2
Samba AD member lost domain join after reboot
...reboots? >> > > Hi, can you post your smb.conf from the domain member. > What OS ? > Does the domain member have a fixed ip or does it use DHCP ? > > Rowland > > -- k Alexis RIES Service informatique Tel : 04.22.32.97.26 Fax : 04.84.25.27.40 Email : alexis.ries at kinaxia.fr http://www.kinaxia.fr -------------- next part -------------- [global] # Enregistrement des logs log file=/var/log/samba/samba.log log level=5 #Informations du domaine netbios name = SMB2 workgroup = SAMDOM security = ADS realm = AD.SAMDOM.LOCAL encrypt passwords = yes #On u...
2016 Jun 07
0
Samba AD member lost domain join after reboot
I was wrong, the problem persists, it is not because of the DNS. You have the same configuration as me, but with two domains controller ? On 07/06/2016 18:05, Alexis RIES wrote: > I think I found my problem, when configuring my second domain > controller, I have created by mistake a round robin DNS entry on > "Forward Lookup Zones -> ad.samdom.local". > I speak of
2016 Jun 08
1
Samba AD member lost domain join after reboot
Hi, I used the DNS management console, right click on zone and "export list". I use Bind9, and yes it is configured. Alexis. On 07/06/2016 18:29, Rowland penny wrote: > On 07/06/16 17:05, Alexis RIES wrote: >> I think I found my problem, when configuring my second domain >> controller, I have created by mistake a round robin DNS entry on >> "Forward Lookup
2016 Jun 07
2
Samba AD member lost domain join after reboot
Yes, the /etc/krb5.keytab file is created when the domain-join. I just noticed that it's not only after a reboot I have this problem. I lost the domain-join on my first SMB server, it has not been restarted. Note that I use Cluster Mode (CTDB), but the problem is the same when I remove the cluster configuration. Attached is the requested files. Thank you, Alexis. On 07/06/2016 09:43,
2016 Jun 08
2
Samba AD member lost domain join after reboot
I conducted many tests and I noticed that I lose the domain-join on SMB1 soon as I joined SMB2 in the domain. Step 1: SMB1 "net ads join -Uadministrator" -> OK Step 2: SMB1 "net ads testjoin" -> OK Step 3: SMB2 "net ads join -Uadministrator" -> OK Step 4: SMB2 "net ads testjoin" -> OK Step 5: SMB1 "net ads testjoin" ->
2016 Jun 08
0
Samba AD member lost domain join after reboot
Hi, You will find attached the output of "net ads testjoin -d4" and "-d3". Yes replication seems to work properly. Alexis. On 07/06/2016 18:55, lingpanda101 at gmail.com wrote: > On 6/7/2016 12:31 PM, Alexis RIES wrote: >> I was wrong, the problem persists, it is not because of the DNS. >> You have the same configuration as me, but with two domains controller