Windows 10 1909/2004 and Samba File Shares
-
Hi Y'all,
At my day job, we've stumbled across something rather interesting as of late... This just started in the last week or two. Some of our Windows 10 systems have started failing to connect to our Samba file server at random. Today it will work, and tomorrow it will not. It seems completely random.
We're running Samba 3.6.3 with SMB2 enabled. The Samba server is a member of our domain, as are the Windows 10 systems trying to access it. I've sen some other reports of this happening between WIndows 10 and some Server 2008 / R2 systems as well.
I'm just checking to see if anybody else has seen this?
-
@dafyre Looking a lot like an SMBv1 issue but what are you getting as errors or warnings.
-
Did you check the logs on both ends to see where the problem is and what the errors are?
-
@dafyre said in Windows 10 1909/2004 and Samba File Shares:
We're running Samba 3.6.3 with SMB2 enabled.
That's very old. Anything keeping you from updating?
-
@scottalanmiller said in Windows 10 1909/2004 and Samba File Shares:
@dafyre said in Windows 10 1909/2004 and Samba File Shares:
We're running Samba 3.6.3 with SMB2 enabled.
That's very old. Anything keeping you from updating?
Yes, we're building a new server as we speak, lol.
-
@dbeato said in Windows 10 1909/2004 and Samba File Shares:
@dafyre Looking a lot like an SMBv1 issue but what are you getting as errors or warnings.
We have disabled SMB1, and forced min & max protocol to be SMB2 in the global config, so I'm not sure that's the issue.
My office machine was having the issue yesterday. Today, it's working. One of my other clients has been having the same issue. We've checked the time synchronization on the systems involved as well. It seems random, too. We've got a couple more tricks up our sleeve to see if we can get it to work. This just started a couple of days ago and we've been tied up with other crap and haven't been able to dive too deeply into it yet.
-
So, wtf do the logs say?
Do IT pros not look at logs anymore or do they keep trying to guess the issue for days until one sticks?
-
@Obsolesce said in Windows 10 1909/2004 and Samba File Shares:
Did you check the logs on both ends to see where the problem is and what the errors are?
We've got to turn the Samba logging up higher, because we're not really getting much by way of details from that log. I'll have my hands on a client machine this afternoon, hopefully, so I'll be able to dig in more then.
-
@Obsolesce said in Windows 10 1909/2004 and Samba File Shares:
So, wtf do the logs say?
Do IT pros not look at logs anymore or do they keep trying to guess the issue for days until one sticks?
Why not? That has worked so well for me in the past!
-
@dafyre said in Windows 10 1909/2004 and Samba File Shares:
@Obsolesce said in Windows 10 1909/2004 and Samba File Shares:
Did you check the logs on both ends to see where the problem is and what the errors are?
We've got to turn the Samba logging up higher, because we're not really getting much by way of details from that log. I'll have my hands on a client machine this afternoon, hopefully, so I'll be able to dig in more then.
Okay, sorry spoke too soon above.
-
That is weird but when things happen out of blue to win10 machines I always start with uninstalling windows updates. In my environment that is by far the number one thing that breaks things. Occasionally a user will do something but if its multiples machines, its always been windows updates here.
