similar to: Windows clients require reboot once a day in order to access mapped drives

Hi Rowland, > I hope someone has seen this before and knows what's going on. Given > > the time delay between the problem recurring, I'm guessing the issue > > lies with Kerberos, but I'm not sure how to verify that or how to > > resolve the issue. If you need more info, please let me know. > > > > Problem: > > Each morning, windows users are

Hai, ... > > As I said, where is the fault, is it something that Windows 10 is or > isn't doing, or is it Samba ? > > Well, we cannot change Windows, so on that basis, I think you should > make a Samba bug report and let it work through the system. > > Rowland Well, yes, we can change windows, by allowing/disallowing SMB1. Which might help in detecting whats

Mason, You can set these also on the share. Win7 and10 client min protocol = SMB2 client max protocol = SMB3 The one for the scanner, client min protocol = NT1 client max protocol = SMB2 Part of my smbstatus -a: PID Username Group Machine Protocol Version Encryption Signing 27316 root root

On Mon, 29 Apr 2019 11:44:22 -0700 Mason Schmitt <mason at ftlcomputing.com> wrote: > > > > > It looks like the issue, with W10 clients needing to reboot each > > > morning to regain access to samba mapped drives, has been worked > > > around with a single smb.conf change. > > > > > > The only change I made (which I did only to help with

On Fri, 26 Apr 2019 15:03:07 -0700 Mason Schmitt via samba <samba at lists.samba.org> wrote: > Hey Rowland and Louis (and anyone else that has been following this > thread), > > It looks like the issue, with W10 clients needing to reboot each > morning to regain access to samba mapped drives, has been worked > around with a single smb.conf change. > > The only

On Mon, 29 Apr 2019 13:01:54 -0700 Mason Schmitt <mason at ftlcomputing.com> wrote: > > > I have another file server, in a different domain, with a nearly > > > identical smb.conf to this one, which does not have an entry for > > > "smb encrypt". According to the man page, this means that it will > > > have "smb encrypt = default".

Hi Rowland, I'm still seeing the problem that I described earlier. I have however uncovered some more information that might help resolve the issue. On Thu, 18 Apr 2019 at 13:10, Mason Schmitt <mason at ftlcomputing.com> wrote: > Hi Rowland, > > > I hope someone has seen this before and knows what's going on. Given >> > the time delay between the problem

> > > Forgot to mention, are sure your time sync over AD is working correctly. > One to add to you list, check times of server and clients, (* yes again, > if needed just to be sure). > Yes, I have double check that time is correctly being synced. FYI, Rowland, the process outlined in the wiki for using chronyd does not work on Ubuntu 18.04 (my AD DC is on Ubuntu, but my file

> > At this point I'm starting to get in over my head and could use some > direction. This looks like a Windows 10 client bug, but given that I can't > see the full SMB conversation (due to encryption) I'm not certain whether > the samba server is replying in the way the client expects. Can you or > someone else help me either find a work around or a resolution?

On Thu, 25 Apr 2019 10:34:24 -0700 Mason Schmitt <mason at ftlcomputing.com> wrote: > > > > > > Forgot to mention, are sure your time sync over AD is working > > correctly. One to add to you list, check times of server and > > clients, (* yes again, if needed just to be sure). > > > > Yes, I have double check that time is correctly being synced.

Hi Mason, On 30.04.2019 19:41, Mason Schmitt wrote: > Hi Viktor, > > I didn't go through all the conversations and I'm not sure if this will > be of any help, I just wanted to inform that I've been using mapped > drives with Windows 10 for ages and never had the problems you > described. I also never added or changed the "smb encrypt"

I didn't go through all the conversations and I'm not sure if this will be of any help, I just wanted to inform that I've been using mapped drives with Windows 10 for ages and never had the problems you described. I also never added or changed the "smb encrypt" option. My Samba file server (AD member) was set up pretty much the way as is described in the official Wiki

Hi Viktor, Do note, > winbind enum users = yes > winbind enum groups = yes Set these to winbind enum users = no winbind enum groups = no It's only slowing down your server and if you need the outputs, use : getent passwd username Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Viktor

Hi Viktor, I didn't go through all the conversations and I'm not sure if this will > be of any help, I just wanted to inform that I've been using mapped > drives with Windows 10 for ages and never had the problems you > described. I also never added or changed the "smb encrypt" option. My > Samba file server (AD member) was set up pretty much the way as is >

Hai, If i may suggest.. AD-DC, fine no changes needed. File server smb.conf, i made some changes, see below. I change the keytab and kerberos methode because your thinking that related to the problem. And i changed some settings below, which are moved from Global setting to Share setting. 3 settings where defined as (S) as in, its a "share" setting, so put it in the share

Forgot to mention, are sure your time sync over AD is working correctly. One to add to you list, check times of server and clients, (* yes again, if needed just to be sure). > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba > Verzonden: donderdag 25 april 2019 9:03 > Aan: samba at lists.samba.org >

On Thu, 25 Apr 2019 10:24:01 -0700 Mason Schmitt via samba <samba at lists.samba.org> wrote: > dedicated keytab file = /etc/krb5.keytab > > kerberos method = secrets and keytab > > > I looked at these earlier in my process and according to the smb.conf > man page, it looks like these commands aren't meant to be used > together (but it won't hurt anything

> > > It looks like the issue, with W10 clients needing to reboot each > > morning to regain access to samba mapped drives, has been worked > > around with a single smb.conf change. > > > > The only change I made (which I did only to help with troubleshooting > > via packet capture) was as follows: > > OLD - smb encrypt = desired > > NEW - smb

> > I have another file server, in a different domain, with a nearly > > identical smb.conf to this one, which does not have an entry for "smb > > encrypt". According to the man page, this means that it will have > > "smb encrypt = default". W10 clients are not able to connect to > > shares, by name, on this file server, after having been idle

Hi Louis, Thanks for your willingness to help! I change the keytab and kerberos methode because your thinking that related > to the problem. dedicated keytab file = /etc/krb5.keytab > kerberos method = secrets and keytab I looked at these earlier in my process and according to the smb.conf man page, it looks like these commands aren't meant to be used together (but it won't