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 several, somet
> 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 sever
> 1. What is your output of testparm?
No errors or warnings, apart from
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
> 2. If you run top, are any Samba related processes (winbindd, smbd, etc)
> consuming excessively high amounts of CPU?
I did not observe this, a
> 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 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 the pointers.
> 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 th
> You might want to take a look at "Integrating Red Hat Enterprise Linux 6 with
> Active Directory". It's the best document I've seen on this topic. I found
> that Samba/Kerberos/Winbind is the most complete solution for attaching a
> Samba fileserver in my AD environment.
> https://access.red
> > 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
> Not sure what would cause that error message, nor have I experienced it.
> Looks like other people have seen it:
> https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+with+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+information:+No+credentials+cache+found
I found no w
Am 14.09.2016 um 17:50 schrieb isdtor :
>
>> Not sure what would cause that error message, nor have I experienced it.
>> Looks like other people have seen it:
>> https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+with+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+informat
On Wed, 2016-09-14 at 16:50 +0100, isdtor wrote:
> > Not sure what would cause that error message, nor have I
> > experienced it. Looks like other people have seen it:
> > https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+wi
> > th+%5BUnspecified+GSS+failure.++Minor+code+may+provide+
On 05/20/2017 06:10 PM, Adam Tauno Williams wrote:
Six months later, now on CentOS6.9, we still see the same issue -
constantly logging this message. Server packages are all up-to-date.
I find multiple reports on the Internet - but no solutions.
The bug report mentioned in the message you re
On Sun, May 21, 2017 at 12:51:50PM -0700, Gordon Messmer wrote:
> The bug report mentioned in the message you replied to indicates that the
> problem was fixed in samba's master branch with this commit:
>
> https://git.samba.org/?p=samba.git;a=commit;h=4d5680e9ae531c6dc4d0a6687abe6293b5d4f4f2
>
>
13 matches
Mail list logo