Hi Denis, We started this whole install/journey with the sernet packages in pf 4.7.0. Then, with pf 5.10 we experienced these problems.
To become more 'main stream' we went back to the wheezy backports samba packages (4.1.17). On our main fileservers/DC's we use only the sernet packages, and we're very happy with those. Anyway, for now I'll retry an install with only wheezy stock items, and see if that gets us any further. Thanks for chiming in! MJ On 6/17/2015 10:40, Denis Bonnenfant diderot wrote: > Le 16/06/2015 21:27, mourik jan heupink a écrit : >> Ok, we have a support contract, but I'd rather keep those incidents for >> when we are in production, and need it more urgently. >> >> Anyway. I'll try a fresh 5.10 install, with only stock samba, to make >> sure that I don't run anything out of the ordinary. >> >> Curious to see if things work as expected then... >> >> > > Hi, > > Maybe it is unrelated, but Debian's Samba 4.1.17 packages introduced > some regressions, and unfortunately upstream patches had not been > included. As a general advice, i strongly encourage you to use Sernet's > repositories, with up-to-date versions 4.1 or 4.2 ( or if you have time, > to help Debian maintainers making samba packages with upstream patches > ). I don't know the exact relations between Samba, Sernet and Debian, > but it seems that most of the packaging work is done by Sernet, and that > Debian package is not actively maintained. > > > Denis > > > > ------------------------------------------------------------------------------ > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
