Hi All, Fedora 276, x64 $ rpm -qa samba\* samba-winbind-clients-4.7.6-0.fc27.x86_64 samba-common-libs-4.7.6-0.fc27.x86_64 samba-client-4.7.6-0.fc27.x86_64 samba-common-tools-4.7.6-0.fc27.x86_64 samba-libs-4.7.6-0.fc27.x86_64 samba-common-4.7.6-0.fc27.noarch samba-4.7.6-0.fc27.x86_64 samba-client-libs-4.7.6-0.fc27.x86_64 samba-winbind-4.7.6-0.fc27.x86_64 samba-dc-libs-4.7.6-0.fc27.x86_64 samba-winbind-modules-4.7.6-0.fc27.x86_64 I just put a Widows Nein, oops Windows Ten computer on a samba based network. Problem: the W-Nein computer can not see any of the other shares. You can manually write in the path and it works fine. The workgroup name is the same for everyone. What did I do wrong? Many thanks, -T
On Fri, 13 Apr 2018 22:31:23 -0700 ToddAndMargo via samba <samba at lists.samba.org> wrote:> Hi All, > > Fedora 276, x64 > > I just put a Widows Nein, oops Windows Ten computer on > a samba based network. > > Problem: the W-Nein computer can not see any of the other > shares. You can manually write in the path and it works fine. > The workgroup name is the same for everyone. > > What did I do wrong? >Probably nothing. I keep saying this, but people are not taking it on board, windows is making it harder & harder to connect to anything other than an AD domain or other windows computer. Your problem isn't a Samba problem, it is possibly because windows has disabled SMBv1 (or NTLMv1 as we call it), though it could be something else, try searching the internet on 'windows 10 not browsing network' Rowland
On 04/14/2018 01:04 AM, Rowland Penny via samba wrote:> On Fri, 13 Apr 2018 22:31:23 -0700 > ToddAndMargo via samba <samba at lists.samba.org> wrote: > >> Hi All, >> >> Fedora 276, x64 >> >> I just put a Widows Nein, oops Windows Ten computer on >> a samba based network. >> >> Problem: the W-Nein computer can not see any of the other >> shares. You can manually write in the path and it works fine. >> The workgroup name is the same for everyone. >> >> What did I do wrong? >> > > Probably nothing. > > I keep saying this, but people are not taking it on board, windows is > making it harder & harder to connect to anything other than an AD > domain or other windows computer. > Your problem isn't a Samba problem, it is possibly because windows has > disabled SMBv1 (or NTLMv1 as we call it), though it could be something > else, try searching the internet on 'windows 10 not browsing network' > > RowlandHi Rowland, Oh I am certain that it is a Windows Nein problem. I just wonder if anyone in these parts knew of a work around. -T