> Other than the original 6.8 release version 3.6.23-33, samba has not been
> functioning correctly for me under 6.8.
>
> The symptoms are that about 6-7 days after starting the server, users start
> complaining that they can no longer open documents on their share. Upon
> inspection, I find
> I have another samba server and upgraded it to samba4. testparm returns
> clean with the old config (ROLE_DOMAIN_PDC) and starts up fine. smbclient
> seems to work fine.
>
> The next thing now is to try and make it a domain member so it can auth
> against AD.
>
> Thanks, Andrew, I appreciate
> > net ads keytab create -U username
> > 8. Verify the contents of the Kerberos keytab file:
> > klist -ke
>
> This is a step I was missing. What is the purpose of the keytab? Can it help
> with the default ticket FILE:/tmp/krb5cc_0 expiration?
A Kerberos keytab contains Kerberos principals and
> Samba 4.x is an intimidating piece of software. If it can perfrom the same
> function and use the same config, I'm willing to try it.
Without log messages or process table info, it's hard to advise any further.
Generally speaking, Samba4 can do everything that Samba 3.6 does. If your
server
> I'm looking to replace an OLD Fedora web server with a Centos 7 one. I'm
> currentlly in the process of documenting what is on the server ready to
> install
> the new one.
>
> While most things have been done with RPMs, some installs have had to be
> done via CPAN for Perl and PEAR for PHP.
>
5 matches
Mail list logo
