samba - Jan 2023 - Solve Err 53 through Samba?

On 17/01/2023 13:51, Gilles via samba wrote:
> Hello
> 
> Is there a simple way on Samba to solve Err 53 when connecting from 
> Windows10 to a guest-enabled server, so I don't have to tweak Windows 
> clients?
What is 'err 53' ?
What version of Windows 10 ? Some of them have guest access turned off 
by default and the only way to get guest access (even to a Samba server) 
is to turn it back on.
> 
> ==================> [global]
>  ??????? bind interfaces only = Yes
>  ??????? interfaces = 192.168.0.15/255.255.255.0 127.0.0.1/255.255.255.255
>  ??????? domain master = Yes
Why set the above line, this isn't a PDC
>  ??????? os level = 255
Again why ? only of any use if you are using network browsing and unless 
you are using an ancient version of Samba, you are not using SMBv1 that 
network browsing relies on.
>  ??????? preferred master = Yes
Again you don't really need the line above
>  ??????? load printers = No
>  ??????? printcap name = /dev/null
>  ??????? guest account = www-data
>  ??????? map to guest = Bad User
>  ??????? security = USER
>  ??????? wins support = Yes
The line above only makes sense if using SMBv1

Rowland

On 17/01/2023 15:07, Rowland Penny via samba wrote:
> What is 'err 53' ?? What version of Windows 10 ? Some of them have 
> guest access turned off by default and the only way to get guest 
> access (even to a Samba server) is to turn it back on.
It occurs when I run "net view \\samba" on a Windows 10 (10.0.19045) 
client. It's an older Samba (4.5.16; Yes, i will upgrade Debian and thus 
Samba in the coming weeks).

I'll turn it on temporarily until I've upgraded Samba.

========c:\Users\joe\Downloads>net view
System error 1231 has occurred. The network location cannot be reached.

c:\Users\joe\Downloads>net view \\samba
System error 53 has occurred. The network path was not found.
========
Thank you.