Good morning everyone,
My name is Luca and I have been using Dietpi for quite some time. I have this problem: in Windows 11, in the network connections, I don’t see the samba shares. To access the shares I have to type \server and in this way I can access.
With OMV I don’t have this problem and the name of the shares are visible among the network resources.
Thanks in advance to those who can help me to solve this problem.
Regards
Did you set a workgroup in the smb.conf?
Do not forget to restart samba after you made changes in the config:
sudo systemctl restart smbd.service nmbd.service
Or you just could map the share as a network drive, then it will be constantly visible in file explorer (I assume this works as well in windows 11 as in windows 10)
Thank you for your answer.
Yes, I have set the same group in both Dietpi and Windows.
I always restart the smbd and nmbd server after the changes.
If I map the shares as disk everything works perfectly.
My problem is that I don’t see the name of the computer (Raspberry + Dietpi) in the network resources of Windows.
Here my [global] smb.conf
[global]
workgroup = DODO
server string = %h server (Samba, Server)
dns proxy = no
log level = 0
log file = /var/log/samba/log.%m
max log size = 1000
logging = syslog
;logging = file
panic action = /usr/share/samba/panic-action %d
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = no
unix password sync = no
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
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
use sendfile = yes
aio read size = 16384
aio write size = 16384
time server = yes
wins support = yes
multicast dns register = no
# Special configuration for Apple's Time Machine
fruit:aapl = yes
# Extra options
min receivefile size = 16384
getwd cache = yes
for what reason you like to see the “computer” on network resources in Windows? It should be fine if it is mounted.
you’re right.
In my network I have several devices that I see in the computer resources (modem, decoder,etc) and I would like to see also the computers that I use as servers (raspberry - dietpi).
With OMV I see the computer (raspberry + OMV) in the Windows resources but I can not do the same with Dietpi.
I wonder why
This one solved it on my test system https://devanswers.co/discover-ubuntu-machines-samba-shares-windows-10-network/
Thank you so much!
You have solved my problem.
Your solution works great!!!
Thanks again
Luca
I had a look to the Github repository for the wsdd tool. Actually it’s quite simple. Just add the repository and install wsdd via apt install
I have two raspberry pi, both with the latest version of Dietpi. I have updated both with the procedure you mentioned.
I have the following situation
- Windows 11 client - I see both raspberry pi’s in the network resources and access them perfectly.
- Manjaro 21.2.2 client - I don’t see the computers in the network resources but only if I type smb://IP_of_the_computer I can access them
- Mint 20.3 client - I only see one raspberry pi in the network resources while to access the other I have to type smb://IP_of_the_computer
What could be the cause?
Regards
Luca
Solution above is dedicated to Windows client. Nor sure what Manjaro or Mint needs to detect Samba server on local network.
Thanks!
It works perfectly with Windows 11.
Luca
Thank you. This is exactly what I was looking for.
Had my pi assigned to a drive but I had to reset the assignments and was wondering why it was not showing up in network.
Interesting discussion, I was just trying to do this the other day. I would like to make my Dietpi box discoverable to my network. I was reading the instructions and there is a part where it says:
There are user-maintained packages for which you need to add the repository to /etc/apt/sources.list.d with a file containing the following line
deb > Index of /public > distro main
Replace distro with the name of your distro, e.g. buster or xenial (issue lsb_release -cs if unsure). After an apt update you can install wsdd with apt install wsdd.
I don’t understand how to add the repository. Is there a command to do that or should I edit the sources.list.d file?
simply create a new source file
nano /etc/apt/sources.list.d/wsdd.list
add following (assuming your are on Debian Bullseye)
deb https://pkg.ltec.ch/public/ bullseye main
and run following to read the list
apt update
Having the same problems on my W11 machine that I don’t see the DietPi machine in my network without mounting the drive.
These commands are the ones to make the DietPi machine directly visible in my network?
create a new source file
nano /etc/apt/sources.list.d/wsdd.list
add following (assuming your are on Debian Bullseye)
deb https://pkg.ltec.ch/public/ bullseye main
and run following to read the list
apt update
install wsdd
apt install wsdd
Yes that should do it.
What about executing a
curl -L https://pkg.ltec.ch/public/conf/ltec-ag.gpg.key | sudo apt-key add -
before executing the apt update?
This avoids the error message regarding missing PUBKEYs (NO_PUBKEY 4BBAE4C69C568C54).
Also, it could be an option
- to add this as an selectable installation option within
dietpi-software - to add this as a hint in the DietPi-Docs
Hi StephanStS,
indeed I get an ‘is not signed’ error.
root@DietPi: nano /etc/apt/sources.list.d/wsdd.list
root@DietPi: apt update
Hit:1 https://deb.debian.org/debian bullseye InRelease
Get:2 https://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Get:4 https://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]
Get:5 https://pkg.ltec.ch/public bullseye InRelease [4317 B]
Hit:6 https://xogium.performanceservers.nl/apt bullseye InRelease
Get:7 https://deb.debian.org/debian bullseye-backports/main arm64 Packages.diff/Index [63.3 kB]
Get:8 https://deb.debian.org/debian bullseye-backports/contrib arm64 Packages.diff/Index [33.0 kB]
Get:9 https://deb.debian.org/debian bullseye-backports/main arm64 Packages T-2023-01-06-0803.55-F-2023-01-06-0209.41.pdiff [24.5 kB]
Get:9 https://deb.debian.org/debian bullseye-backports/main arm64 Packages T-2023-01-06-0803.55-F-2023-01-06-0209.41.pdiff [24.5 kB]
Get:10 https://deb.debian.org/debian bullseye-backports/contrib arm64 Packages T-2023-01-06-0803.55-F-2023-01-06-0803.55.pdiff [641 B]
Get:10 https://deb.debian.org/debian bullseye-backports/contrib arm64 Packages T-2023-01-06-0803.55-F-2023-01-06-0803.55.pdiff [641 B]
Err:5 https://pkg.ltec.ch/public bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4BBAE4C69C568C54
Reading package lists... Done
W: GPG error: https://pkg.ltec.ch/public bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4BBAE4C69C568C54
E: The repository 'https://pkg.ltec.ch/public bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@DietPi:/mnt/dietpi_userdata/nzbget# apt install wsdd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package wsdd
root@DietPi:
With tour suggestion:
root@DietPi:/mnt/dietpi_userdata/nzbget# cd /
root@DietPi:/# curl -L https://pkg.ltec.ch/public/conf/ltec-ag.gpg.key | sudo apt-key add -
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1686 100 1686 0 0 13933 0 --:--:-- --:--:-- --:--:-- 13933
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
root@DietPi:/#
root@DietPi:/# apt update
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
Get:5 https://pkg.ltec.ch/public bullseye InRelease [4317 B]
Hit:6 https://armbian.hosthatch.com/apt bullseye InRelease
Get:7 https://pkg.ltec.ch/public bullseye/main arm64 Packages [428 B]
Fetched 4745 B in 3s (1435 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@DietPi:/# apt install wsdd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
wsdd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.4 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://pkg.ltec.ch/public bullseye/main arm64 wsdd all 0.7.0 [21.4 kB]
Fetched 21.4 kB in 0s (44.5 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package wsdd.
(Reading database ... 28209 files and directories currently installed.)
Preparing to unpack .../archives/wsdd_0.7.0_all.deb ...
Unpacking wsdd (0.7.0) ...
Setting up wsdd (0.7.0) ...
Created symlink /etc/systemd/system/multi-user.target.wants/wsdd.service → /lib/systemd/system/wsdd.service.
INFO: please configure wsdd in /etc/wsdd.conf before starting
root@DietPi:/#
1 Like
I also configured /etc/systemd/system/wsdd.service with this contents:
[Unit]
Description=Web Services Dynamic Discovery host daemon
; Start after the network has been configured
After=network-online.target
Wants=network-online.target
; It makes sense to have Samba running when wsdd starts, but is not required
;Wants=smb.service
[Service]
Type=simple
ExecStart=/usr/bin/wsdd --shortlog
; Replace those with an unprivledged user/group that matches your environment,
; like nobody/nogroup or daemon:daemon or a dedicated user for wsdd
User=daemon
Group=daemon
; The following lines can be used for a chroot execution of wsdd.
; Also append '--chroot /run/wsdd/chroot' to ExecStart to enable chrooting
;AmbientCapabilities=CAP_SYS_CHROOT
;ExecStartPre=/usr/bin/install -d -o nobody -g nobody -m 0700 /run/wsdd/chroot
;ExecStopPost=rmdir /run/wsdd/chroot
[Install]
WantedBy=multi-user.target
After this, systemctl status wsdd showed a running system:
● wsdd.service - Web Services Dynamic Discovery host daemon
Loaded: loaded (/etc/systemd/system/wsdd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-01-06 12:12:52 CET; 3min 50s ago
Main PID: 569 (python3)
Tasks: 1 (limit: 2320)
Memory: 23.6M
CPU: 686ms
CGroup: /system.slice/wsdd.service
└─569 python3 /usr/bin/wsdd --shortlog
Jan 06 12:12:52 smbserver systemd[1]: Started Web Services Dynamic Discovery host daemon.
Jan 06 12:12:53 smbserver wsdd[569]: WARNING: no interface given, using all interfaces
I kept /etc/wsdd.conf as it is.