Question Samba share doens't appear at network section RRS feed

Jul 20, 2020
I am trying to reach my samba server although does not appear on network selection and I have to do this manually from PowerShell


or from file manager adding this on address bar.


Older versions of windows reach the server at network section
although windows 10 they don't. Is a feature that I want back because
make thing harder for my colleagues

I can reacah server Via Ping

ping serverhome

Pinging serverhome [] with 32 bytes of data:
Reply from bytes=32 time<1ms TTL=64
Reply from bytes=32 time<1ms TTL=64
Reply from bytes=32 time<1ms TTL=64
Reply from bytes=32 time<1ms TTL=64

Ping statistics for
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

My configuration on server

workgroup = WORKGROUP
server string = %h server (Samba, Ubuntu)
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
panic action = /usr/share/samba/panic-action %d
server role = standalone server
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully .
pam password change = yes
map to guest = never
restrict anonymous = 2
usershare allow guests = yes
server min protocol = SMB2_10
client min protocol = SMB2_10
client max protocol = SMB3
encrypt passwords = true
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no

path= /media/HDD/SF/MANOS
browseable= yes
read only = no
valid users = manos
guest ok = no

  • My PCs run windows 10 pro 2004
  • My Server rum Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-109-generic x86_64)
  • They are on same subnet 192.168.1.x/24


Win 10 Master
It appears the blame is actually Ubuntu doesn't include a program, installed by default, that would allow it to show windows 10 the servers. Installing 1 program on Ubuntu, fixes it as shown in the 1st link below.
With Windows 10 version 1511, support for SMBv1 and thus NetBIOS device discovery was disabled by default. Depending on the actual edition, later versions of Windows starting from version 1709 (“Fall Creators Update”) do not allow the installation of the SMBv1 client anymore.

This causes hosts running Samba not to be listed in the Explorer’s “Network (Neighborhood)” views. While there is no connectivity problem and Samba will still run fine, users might want to have their Samba hosts to be listed by Windows automatically.
This appears to be solution -
Last edited: