Created attachment 13547 [details]
Samba Config File
Server OS: CentOS 6.9, all latest patches.
Client OS: Windows 7 Professional, all latest patches
Not sure whether this is a bug or whether I am doing something incorrect, please advice of the latter.
When I UNSET "min protocol" or set to "min protocol = SMB1" all is fine and I can see every machine, device and printers on the network.
When I SET "min protocol = SMB2" I get nothing, all network folders are empty, even when browsing as "root" or "domain admin" I cannot see anything.
I use loads of scripts on my windows own client (my workstation) do do my daily deed, many of those scripts use "Net session" or "Net view" - I cannot use these scripts when I have set the minimum protocol to SMB2 - it does not reveal anything on the network.
I also cannot browse (like editing remote registries etc) - which makes life a little tricky.
I also believe in security, so simply switching back ain't easy for me.
So is this a bug?
Sorry forgot to add.
This has been a problem for me for a while but I waited till I had some time to upgrade the server from 3.6.X to 4.1.X because I thought it maybe 3.6.x related.
But the upgrade did not change a thing.
at least with recent Samba releases printing is also known to work well with SMB2/SMB3 enabled and clients not having SMB1 enabled any more. If this is an issue in your particular setup you might want to look for help on the samba mailing list or professional support like listed on https://www.samba.org/samba/support/globalsupport.html