[Samba] [Windows 10] Error 1231?
rpenny at samba.org
Mon Dec 12 09:03:15 UTC 2022
On 12/12/2022 03:38, Gilles via samba wrote:
> For years, I've successfully used a Windows7 host at home to connect to
> a couple of Debian hosts running Samba 4. One of those ("debian_wins",
> running 4.5.16) is acting as the master browser as well as sharing
> folders, while the second ("debian_server") is just sharing folders.
> I've recently added a Windows10 host, and notice the following things
> when working on that host:
> 1. "net view" triggers error 1231. Enabling Network discovery on the
> Windows10 host makes no difference
> 2. net view \\debian_wins triggers error 53
> 3. net view \\debian_server works OK, as well as "net use x:
> \\debian_server\myshare. I can read/write with no problem.
> FWIW, on the Windows10 host, I boot up without typing a password; I
> don't remember if I used an empty password or just a dummy password (eg.
> What do you suggest I try on the Windows10 host and/or the debian_wins
> server to solve those issues?
Absolutely Nothing on the Windows side.
However, on the Linux side, I would suggest you upgrade everything. You
appear to still be using Stretch, which is EOL as far as Debian is
concerned. Samba 4.15.6 is definitely EOL, the latest Samba version is
4.17.3 . You also seem to be running Samba as a quasi PDC, but only with
(or so it seems) guest access. The use of 'wins' etc is virtually dead.
As you probably do not want to run an AD domain, can I suggest you
upgrade everything, run a standalone server (without wins etc) using
Avahi for the Linux clients and wsdd for the Windows clients.
More information about the samba