I just had an issue with automounter not being about to mount windows
shares after upgrading all the rpms on some of my centos 6.x servers..
I haven't seen the fix here yet so I thought I'd throw it out there..
as a workaround edit the smb.conf file like so:
[global]
client use spnego = no
On 05/11/2016 11:39 AM, Philippe BOURDEU d'AGUERRE wrote:
Workaround with smb.conf parameters given here seems to work but it
works only for accounts already existing in the domain.
New accounts get a "There are currently no logon servers available to
service the logon" message.
I have downgrad
Another follow up.
I have a Centos 6 server running as a Samba NT4/PDC Domain controller
and have seen the regression with 3.6.23-30 release.
Client is a Windows 2008R2 server.
Workaround with smb.conf parameters given here seems to work but it
works only for accounts already existing in the
Just to follow up, the fix for us was to add "client ipc signing = auto" to
our smb.conf configuration file.
On Wed, Apr 13, 2016 at 1:17 PM, Bill Baird
wrote:
> FYI: https://lists.samba.org/archive/samba/2016-April/199013.html
>
> On Wed, Apr 13, 2016 at 12:53 PM, Bill Baird
> wrote:
>
>> I'm
On 04/16/2016 05:54 PM, Bob Smith wrote:
client signing = required
server signing = auto
Thanks, this worked for me, too.
Mogens
--
Mogens Kjaer, m...@lemo.dk
http://www.lemo.dk
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mai
On 04/13/2016 03:10 PM, Steven Ford wrote:
Did you update your Windows clients?
They run Windows Update automatically.
They might not have got the update when the server was updated.
Is this the key point?
Mogens
--
Mogens Kjaer, m...@lemo.dk
http://www.lemo.dk
_
On 04/14/2016 12:05 AM, Bob Smith wrote:
I had exactly the same problem. Your workaround fixed me too.
With the new samba packages my samba\logs are full of errors.
If I temporarily disconnected the PC client NIC cable, and
logged into the domain using cached credentials, then I could
get past
Slightly OT. A Windows NT4 PDC? Wow. I applaud you, sir!
That is a name I've not heard in a long time.
On Wed, Apr 13, 2016 at 12:53 PM, Bill Baird
wrote:
> I'm seeing the exact same behavior in my environment (NT4 PDC, not AD). I
> had to downgrade samba get systems working again.
>
> The f
FYI: https://lists.samba.org/archive/samba/2016-April/199013.html
On Wed, Apr 13, 2016 at 12:53 PM, Bill Baird
wrote:
> I'm seeing the exact same behavior in my environment (NT4 PDC, not AD). I
> had to downgrade samba get systems working again.
>
> The full error message is:
>
> "The trust rela
I'm seeing the exact same behavior in my environment (NT4 PDC, not AD). I
had to downgrade samba get systems working again.
The full error message is:
"The trust relationship between this workstation and the primary domain
failed".
Did you have any luck finding a solution?
__
Did you update your Windows clients?
On Wed, Apr 13, 2016 at 1:51 AM, Mogens Kjaer wrote:
> Hello,
>
> I run a CentOS 6 machine with samba, serving approx. 150 Windows users
> with samba running as an NT-like PDC.
>
> After today's samba update (samba-3.6.23-30.el6_7.x86_64 etc.), nobody can
>
yum history undo?
Von meinem iPhone gesendet
> Am 13.04.2016 um 07:51 schrieb Mogens Kjaer :
>
> Hello,
>
> I run a CentOS 6 machine with samba, serving approx. 150 Windows users with
> samba running as an NT-like PDC.
>
> After today's samba update (samba-3.6.23-30.el6_7.x86_64 etc.), nobody
12 matches
Mail list logo
