samba - Jun 2018 - two samba servers just stopped working :-(

I have two samba centos7 samba server VMs.  One at work, one at home.

 

These are ansible servers and I have a share on them that I mount from
windows 10 workstations where I use sublime text to edit my playbooks.

 

They are domain joined (different domains) and use AD authentication - think
they are setup with Kerberos iirc , sssd realmd.

 

So this was all working find two weeks ago, then day before yesterday I
tried to access the shares and it says windows cannot access bla bla bla, 

 

The logs look fairly normal but end 

  Unlocking key 63BB9DA4

[2018/06/13 12:49:08.624451,  4, pid=29487, effective(0, 0), real(0, 0)]
../source3/smbd/sec_ctx.c:320(set_sec_ctx_internal)

  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0

[2018/06/13 12:49:08.624481,  5, pid=29487, effective(0, 0), real(0, 0)]
../libcli/security/security_token.c:53(security_token_debug)

  Security token: (NULL)

[2018/06/13 12:49:08.624510,  5, pid=29487, effective(0, 0), real(0, 0)]
../source3/auth/token_util.c:651(debug_unix_user_token)

  UNIX token of user 0

  Primary group is 0 and contains 0 supplementary groups

[2018/06/13 12:49:08.624559,  5, pid=29487, effective(0, 0), real(0, 0)]
../source3/smbd/uid.c:425(smbd_change_to_root_user)

  change_to_root_user: now uid=(0,0) gid=(0,0)

[2018/06/13 12:49:08.625298, 10, pid=29487, effective(0, 0), real(0, 0)]
../source3/lib/messages_dgm_ref.c:157(msg_dgm_ref_destructor)

  msg_dgm_ref_destructor: refs=(nil)

[2018/06/13 12:49:08.625493,  3, pid=29487, effective(0, 0), real(0, 0)]
../source3/smbd/server_exit.c:248(exit_server_common)

  yn at standardbikerepair.comerver <mailto:yn at
standardbikerepair.comerver>
exit (NT_STATUS_CONNECTION_RESET)

 

 

 


With the NT_STATUS_CONNECTION_RESET

 

I've googled on this and nothing comes up that matches what is happening to
me.  I have tried windows 7 and 3 windows 10 workstation and its all the
same. 

 

They are still joined to the domain and I can login with ssh using domain
creds.  Nothing changed on smb conf setup.  

 

I know this is pretty vauge - I've followed some trouble shooting steps.

 

Smbclient -L lists it fine, firewall is turned off, selinux is disabled.
The fact they both quit working at about the same time seems to point to
windows updates,  I don't think I ran yum update on them - doubtful that I
would have run on both especially. maybe a windows update?  But seems like
a lot more people would be asking this.   Appreciate any ideas on this I can
try.

 

Interesting, I just tried to login with the smbclient and the ad user I ssh
in with and that tells me NT_STATUS_NO_LOGON_SERVERS 

 

Yet I can still authenticate my AD GUID for SSH so that message must be
wrong.

 

 

 

Regards, Bill

 

Bill Dossett

DevOps Ninja

AWS-DevOps-Pro
<https://aws.amazon.com/certification/certified-devops-engineer-professional
/> ,
<https://aws.amazon.com/certification/certified-solutions-architect-associat
e/> AWS-SA-A
<http://mylearn.vmware.com/mgrReg/plan.cfm?plan=30483&ui=www_cert>
VCAP-DCA,
<http://mylearn.vmware.com/mgrReg/plan.cfm?plan=30484&ui=www_cert>
VCAP-DCD,
MCSA Win Server