I was going to try Samba4, but when I tried to install via yum it said it conflicted with samba 3. When I tried to remove samba 3, it said packetfence.noarch depended on it. I decided to try something else to avoid breaking dependencies.
Last week, using yum I upgraded to Centos 6.7. Today, just like clockwork AD authentication started failing 7 days after the join. Here are the samba packages I have installed: yum list installed | grep samba samba.x86_64 3.6.23-20.el6 @base samba-client.x86_64 3.6.23-20.el6 @base samba-common.x86_64 3.6.23-20.el6 @base samba-winbind.x86_64 3.6.23-20.el6 @base samba-winbind-clients.x86_64 3.6.23-20.el6 @base samba4-libs.x86_64 4.0.0-66.el6_6.rc4 @updates There is a package samba-winbind-krb5-locator.x86_64 that is available, but not installed. Redhat describes this package as "It contains a plug-in for the system Kerberos library to allow the local Kerberos library to use the same KDC as Samba and Winbind use." Is this package required? One thing I did notice was that in my /chroots/MGA/etc/samba/MGA.conf and /chroots/MGADomain/etc/krb5.conf the realm was listed in lowercase. Everything I've read states it should always be the domain in UPPERCASE. Today, I deleted the existing domain in the Packetfence GUI and created a new one where I input the domain in UPPERCASE. I'll see if it lasts more than a week. ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
