Hi there
I recently reinstalled Arch Linux on my main desktop and I just kept my personal files. Everything else was a «new fresh installation».
Now I just can’t start the samba service. First there was a problem with a missing directory (/usr/local/samba/var) but I created the directory and it solved the problem. However another weird problem is still persisting, even after I updated the system with a «pacman -Syu»:
Sep 12 21:30:07 phoenix systemd[1]: Starting Samba SMB Daemon...
Sep 12 21:30:07 phoenix smbd[810]: [2018/09/12 21:30:07.926941, 0] ../lib/param/loadparm.c:1610(set_variable_helper)
Sep 12 21:30:07 phoenix smbd[810]: set_variable_helper(not): value is not boolean!
Sep 12 21:30:07 phoenix systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Sep 12 21:30:07 phoenix systemd[1]: smb.service: Failed with result 'exit-code'.
Sep 12 21:30:07 phoenix systemd[1]: Failed to start Samba SMB Daemon.The same problem appears with «testparm»:
...
set_variable_helper(not): value is not boolean!
Error loading services.My CPU is a AMD Ryzen 7 1700X Eight-Core Processor with 16Gb of RAM.
Any ideas?
Kind regards
Last edited by cmmps (2018-09-12 22:05:14)
On Ubuntu 18.04 whenever I do apt upgrade (even if no packages to upgrade):
root@JohnPC:/home/john# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.2)
…
Samba is not being run as an AD Domain Controller.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc.service.
Job for smbd.service failed because the control process exited with error code.
See "systemctl status smbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript smbd, action "restart" failed.
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-08-17 08:13:54 BST; 27ms ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 28404 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 28404 (code=exited, status=1/FAILURE)
Aug 17 08:13:54 JohnPC systemd[1]: Starting Samba SMB Daemon...
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Failed with result 'exit-code'.
Aug 17 08:13:54 JohnPC systemd[1]: Failed to start Samba SMB Daemon.
dpkg: error processing package samba (--configure):
installed samba package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@JohnPC:/home/john# systemctl status smbd.service
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-08-17 08:13:54 BST; 43s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 28404 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, st
Main PID: 28404 (code=exited, status=1/FAILURE)
Aug 17 08:13:54 JohnPC systemd[1]: Starting Samba SMB Daemon...
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Aug 17 08:13:54 JohnPC systemd[1]: smbd.service: Failed with result 'exit-code'.
Aug 17 08:13:54 JohnPC systemd[1]: Failed to start Samba SMB Daemon.
Scorch
4111 gold badge6 silver badges13 bronze badges
asked Aug 17, 2018 at 7:19
4
Open a terminal and run the following command:
testparm -s
Do you get the following error:
WARNING: Ignoring invalid value 'share' for parameter 'security'
Error loading services.
If you do edit /etc/samba/smb.conf, find the line «security = share», and delete it. Then rerun systemctl status smbd.service.
It could be another parameter that is the culprit but that is the most common. In all cases testparm should give you a hint to the offending parameter and end with the «Error loading services» error.
EDIT: If you have no smb.conf at /etc/samba but have one at /usr/share/samba then copy that one to the standard location:
sudo cp /usr/share/samba/smb.conf /etc/samba
Run «testparm -s» again to make sure it’s happy.
answered Aug 17, 2018 at 11:52
Morbius1Morbius1
6,5611 gold badge11 silver badges20 bronze badges
9
Same problem over here. The nmbd-logfile complaint about some problems with netbios on ipv6. So I checked smb.conf and at [globals] I found that the interface was bound to ‘eth*’ but my interface name is ‘enp0s31f6’. After changing this smbd and nmbd started both fine. Also my ‘apt-get upgrade’ problem was gone 🙂
answered Feb 17, 2019 at 18:18
I had the same problem and changed the bound interface in smb.conf from eno0 to eno1 (my actual interface), but the problem was still there.
Then I realised there was a smb.conf.ucf-dist in the same folder /etc/samba which had a wrong interface bound eth0.
I changed it to eno1, saved and then could apt update & upgrade without having the problem any more … Look like some config or all of it is taken from this file if it exists in the folder.
Kevin Bowen
19.1k55 gold badges75 silver badges81 bronze badges
answered Oct 31, 2020 at 10:00
I was able to workaround the installation failure by using systemd-tmpfiles to create the missing directory:
+bryan@bryanNAS:~$ sudo dpkg —configure -a
Setting up samba-common-bin (2:4.11.6+dfsg-0ubuntu1.3) …
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
ERROR: lock directory /run/samba does not exist
ERROR: pid directory /run/samba does not exist
WARNING: some services use vfs_fruit, others don’t. Mounting them in conjunction on OS X clients results in undefined behaviour.
Server role: ROLE_STANDALONE
dpkg: error processing package samba-common-bin (—configure):
installed samba-common-bin package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of samba:
samba depends on samba-common-bin (= 2:4.11.6+dfsg-0ubuntu1.3); however:
Package samba-common-bin is not configured yet.
dpkg: error processing package samba (—configure):
dependency problems — leaving unconfigured
Errors were encountered while processing:
samba-common-bin
samba
+bryan@bryanNAS:~$ sudo /bin/systemd-tmpfiles —create /usr/lib/tmpfiles.d/samba.conf
+bryan@bryanNAS:~$ sudo dpkg —configure -a
Setting up samba-common-bin (2:4.11.6+dfsg-0ubuntu1.3) …
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
WARNING: some services use vfs_fruit, others don’t. Mounting them in conjunction on OS X clients results in undefined behaviour.
Server role: ROLE_STANDALONE
Done
Setting up samba (2:4.11.6+dfsg-0ubuntu1.3) …
Installing new version of config file /etc/init.d/nmbd …
Installing new version of config file /etc/init.d/samba-ad-dc …
Installing new version of config file /etc/init.d/smbd …
Installing new version of config file /etc/logrotate.d/samba …
Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-ad-dc.service already masked)
Removing obsolete conffile /etc/init.d/samba …
Removing obsolete conffile /etc/init/nmbd.conf …
Removing obsolete conffile /etc/init/reload-smbd.conf …
Removing obsolete conffile /etc/init/samba-ad-dc.conf …
Removing obsolete conffile /etc/init/smbd.conf …
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
samba-ad-dc.service is a disabled or a static unit not running, not starting it.
Processing triggers for libc-bin (2.31-0ubuntu9) …
Processing triggers for systemd (245.4-4ubuntu3.1) …
Processing triggers for ureadahead (0.100.0-21) …
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jul 2 17:08:23 2020
ErrorMessage: installed samba-common-bin package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2017-08-20 (1047 days ago)
InstallationMedia: Ubuntu 17.04 «Zesty Zapus» — Release amd64 (20170412)
OtherFailedConnect: Yes
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SambaServerRegression: Yes
SmbConfIncluded: No
SourcePackage: samba
TestparmExitCode: 0
Title: package samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-07-02 (0 days ago)
- Forum
- The Ubuntu Forum Community
- Ubuntu Specialised Support
- Ubuntu Servers, Cloud and Juju
- Server Platforms
- [SOLVED] after 18.04 upgrade smbd won’t start
-
after 18.04 upgrade smbd won’t start
Getting this error when trying to start smbd:
Jul 28 09:14:16 King-Arthur systemd[1]: Starting Samba NMB Daemon…
Jul 28 09:14:16 King-Arthur systemd[1]: nmbd.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 09:14:16 King-Arthur systemd[1]: nmbd.service: Failed with result ‘exit-code’.
Jul 28 09:14:16 King-Arthur systemd[1]: Failed to start Samba NMB Daemon.
Jul 28 09:14:16 King-Arthur systemd[1]: Starting Samba NMB Daemon…
Jul 28 09:14:17 King-Arthur systemd[1]: nmbd.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 09:14:17 King-Arthur systemd[1]: nmbd.service: Failed with result ‘exit-code’.
Jul 28 09:14:17 King-Arthur systemd[1]: Failed to start Samba NMB Daemon.
Jul 28 09:14:28 King-Arthur systemd[1]: Starting Samba SMB Daemon…
Jul 28 09:14:28 King-Arthur systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 09:14:28 King-Arthur systemd[1]: smbd.service: Failed with result ‘exit-code’.
Jul 28 09:14:28 King-Arthur systemd[1]: Failed to start Samba SMB Daemon.
Jul 28 09:14:29 King-Arthur systemd[1]: Starting Samba SMB Daemon…
Jul 28 09:14:29 King-Arthur systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 09:14:29 King-Arthur systemd[1]: smbd.service: Failed with result ‘exit-code’.
Jul 28 09:14:29 King-Arthur systemd[1]: Failed to start Samba SMB Daemon.My googling hasn’t got me anywhere….
The message is pretty generic where can I get some better info about what the issue is?Thanks in advance,
Peter
-
Re: after 18.04 upgrade smbd won’t start
How about ‘sudo systemctl status smbd’? Does that give you more info?
Or the samba logs?
-
Re: after 18.04 upgrade smbd won’t start
I don’t think that is any more helpful:
● smbd.service — Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-07-28 09:14:29 EDT; 2h 34min ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 2195 ExecStart=/usr/sbin/smbd —foreground —no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 2195 (code=exited, status=1/FAILURE)Jul 28 09:14:29 King-Arthur.xxx.name systemd[1]: Starting Samba SMB Daemon…
Jul 28 09:14:29 King-Arthur.xxx.name systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 09:14:29 King-Arthur.xxx.name systemd[1]: smbd.service: Failed with result ‘exit-code’.
Jul 28 09:14:29 King-Arthur.xxx.name systemd[1]: Failed to start Samba SMB Daemon.
-
Re: after 18.04 upgrade smbd won’t start
It is fairly easy to reproduce that output from sudo systemctl status smbd however.
Run this command:
Do you get this as the output:
Code:
WARNING: Ignoring invalid value 'share' for parameter 'security' Error loading services.
If you do, edit /etc/samba/smb.conf, find the line security = share, and either delete it or change it to security = user.Save the file then restart smbd.
-
Re: after 18.04 upgrade smbd won’t start
This has worked for me, this was on upgrade to 17.10:
Code:
sudo systemctl disable nmbd sudo systemctl disable smbd sudo systemctl unmask samba-ad-dc sudo systemctl enable samba-ad-dc
Also check your permissions on:
Code:
cd /var/lib/samba/private && ls -la
I had noticed that somehow they changed on mine from 755 to 700.and should be @ 755
EDIT Never mind Morbius1 has the right solution.
Last edited by 1fallen; July 28th, 2018 at 05:17 PM.
With realization of one’s own potential and self-confidence in one’s ability, one can build a better world.
Dalai Lama>>
Code Tags Arch Linux, openSuse Tumbleweed
-
Re: after 18.04 upgrade smbd won’t start
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Unknown parameter encountered: «announce version»
Ignoring unknown parameter «announce version»
WARNING: The «null passwords» option is deprecated
handle_name_resolve_order: WARNING: Ignoring invalid list value ‘hosts’ for parameter ‘name resolve order’
Error loading services.So hosts got changed to host?
Also is there any issues connecting from an XP machine to the new version of Samba?
-
Re: after 18.04 upgrade smbd won’t start
Um …. there’s 2 ways we can go from here:
[1] Post the entire contents of /etc/samba/smb.conf and we can go line by line and update / correct it.
[2] Reset yourself to the new default:
Make a copy of the one you have:
Code:
sudo mv /etc/samba/smb.conf /etc/samba/smb.conf.orig
Copy the default that is present on you system for times like this:
Code:
sudo cp -a /usr/share/samba/smb.conf /etc/samba/
Before making changes to it for things like name resolve order, etc run this command again and make sure it’s clean:
-
Re: after 18.04 upgrade smbd won’t start
Well lets start with my file:
Thanks again.
And it is working from Win7 and not from my XP machine….yeah I know i need to upgrade it.
[global]
; General server settings
netbios name = king-arthur
server string =
workgroup = xxx
;announce version = 5.0
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192passdb backend = tdbsam
security = user
;null passwords = true
username map = /etc/samba/smbusers
name resolve order = host wins bcastwins support = yes
printing = CUPS
printcap name = CUPSsyslog = 1
syslog only = yes
follow symlinks = yes
wide links = yes
unix extensions = no; NOTE: If you need access to the user home directories uncomment the
; lines below and adjust the settings to your hearts content.
;[homes]
;valid users = %S
;create mode = 0600
;directory mode = 0755
;browseable = no
;read only = no
;veto files = /*.{*}/.*/mail/bin/; NOTE: Only needed if you run samba as a primary domain controller.
; Not needed as this config doesn’t cover that matter.
;[netlogon]
;path = /var/lib/samba/netlogon
;admin users = Administrator
;valid users = %U
;read only = no; NOTE: Again — only needed if you’re running a primary domain controller.
;[Profiles]
;path = /var/lib/samba/profiles
;valid users = %U
;create mode = 0600
;directory mode = 0700
;writeable = yes
;browseable = no; NOTE: Inside this place you may build a printer driver repository for
; Windows — I’ll cover this topic in another HOWTO.[ftp]
path = /var/ftp/
browseable = yes
read only = no
guest ok = no
create mask = 0644
directory mask = 0755
force user = ftpuser
force group = ftpuser
-
Re: after 18.04 upgrade smbd won’t start
Samba doesn’t recommend you do the «socket options» thing any longer. Keep it in for now and if there are any issues remove it.
Looks like you fixed the name resolve order problem.
The WinXP client is a problem. I realize that even today there are more WinXP users than Desktop Linux users but Samba has moved on. I’m going to guess that if you add the following to the [global] section it will bring your server to the security level it was back then:
Code:
lanman auth = yes ntlm auth = yes
Restart smbd and pray.
-
Re: after 18.04 upgrade smbd won’t start
Originally Posted by Morbius1
Samba doesn’t recommend you do the «socket options» thing any longer. Keep it in for now and if there are any issues remove it.
Looks like you fixed the name resolve order problem.
The WinXP client is a problem. I realize that even today there are more WinXP users than Desktop Linux users but Samba has moved on. I’m going to guess that if you add the following to the [global] section it will bring your server to the security level it was back then:
Code:
lanman auth = yes ntlm auth = yes
Restart smbd and pray.
+1
to make Windows XP able to connect to my Samba server I had to add:Code:
server max protocol = NT1 lanman auth = yes ntlm auth = yes
and without these lines Android 7 wasn’t able to access the share neither.
With realization of one’s own potential and self-confidence in one’s ability, one can build a better world.
Dalai Lama>>
Code Tags Arch Linux, openSuse Tumbleweed
Bookmarks
Bookmarks
Posting Permissions
-
Crispin
- Posts: 8
- Joined: Thu Oct 18, 2012 11:59 pm
RPi 4 — Samba installed but service won’t start
Hi folks,
I have a RPi4 — 4GB
I can’t get samba working on it which is normally very easy.
Here are some details
- It’s Buster lite
- It’s a fresh, updated install
- All I have installed in OpenJDK 8
- I’ve gone through the install — always followed this guy’s blog
- install is simply sudo apt-get install samba samba-common-bin
- All the above is done logged in as root.
I get the following in while installing
Code: Select all
Setting up libcephfs2:armhf (12.2.11+dfsg1-2.1+rpi1) ...
Setting up libgfapi0:armhf (5.5-3) ...
Setting up samba-common-bin (2:4.9.5+dfsg-5) ...
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
Error loading services.
dpkg: error processing package samba-common-bin (--configure):
installed samba-common-bin package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of samba:
samba depends on samba-common-bin (= 2:4.9.5+dfsg-5); however:
Package samba-common-bin is not configured yet.
dpkg: error processing package samba (--configure):
dependency problems - leaving unconfigured
Processing triggers for systemd (241-5+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Errors were encountered while processing:
samba-common-bin
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@raspberrypi:~#
After that, I’m stuck 
Any help appreciated.
-
fruitoftheloom
- Posts: 27225
- Joined: Tue Mar 25, 2014 12:40 pm
Re: RPi 4 — Samba installed but service won’t start
Sat Jun 29, 2019 5:25 am
Crispin wrote: ↑
Sat Jun 29, 2019 5:16 am
Hi folks,I have a RPi4 — 4GB
I can’t get samba working on it which is normally very easy.
Here are some details
- It’s Buster lite
- It’s a fresh, updated install
- All I have installed in OpenJDK 8
- I’ve gone through the install — always followed this guy’s blog
- install is simply sudo apt-get install samba samba-common-bin
- All the above is done logged in as root.
I get the following in while installing
Code: Select all
Setting up libcephfs2:armhf (12.2.11+dfsg1-2.1+rpi1) ... Setting up libgfapi0:armhf (5.5-3) ... Setting up samba-common-bin (2:4.9.5+dfsg-5) ... Checking smb.conf with testparm Load smb config files from /etc/samba/smb.conf Error loading services. dpkg: error processing package samba-common-bin (--configure): installed samba-common-bin package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of samba: samba depends on samba-common-bin (= 2:4.9.5+dfsg-5); however: Package samba-common-bin is not configured yet. dpkg: error processing package samba (--configure): dependency problems - leaving unconfigured Processing triggers for systemd (241-5+rpi1) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-10+rpi1) ... Errors were encountered while processing: samba-common-bin samba E: Sub-process /usr/bin/dpkg returned an error code (1) root@raspberrypi:~#After that, I’m stuck
Any help appreciated.
OpenJDK8 is not in the Buster repositories, it is OpenJDK11
Code: Select all
sudo apt update
sudo apt full-upgrade
sudo rebootCode: Select all
sudo apt update
sudo apt install samba-common-binLast edited by fruitoftheloom on Sat Jun 29, 2019 5:29 am, edited 3 times in total.
Take what I advise as advice not the utopian holy grail, and it is gratis !!
-
Crispin
- Posts: 8
- Joined: Thu Oct 18, 2012 11:59 pm
Re: RPi 4 — Samba installed but service won’t start
Sat Jun 29, 2019 5:28 am
I’ve done a purge and and reinstall — below is a new error as part of the reinstall
Code: Select all
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package python-dnspython.
(Reading database ... 48119 files and directories currently installed.)
Preparing to unpack .../00-python-dnspython_1.16.0-1_all.deb ...
Unpacking python-dnspython (1.16.0-1) ...
Selecting previously unselected package python-crypto.
Preparing to unpack .../01-python-crypto_2.6.1-9+b1_armhf.deb ...
Unpacking python-crypto (2.6.1-9+b1) ...
Selecting previously unselected package libtdb1:armhf.
Preparing to unpack .../02-libtdb1_1.3.16-2+b1_armhf.deb ...
Unpacking libtdb1:armhf (1.3.16-2+b1) ...
Selecting previously unselected package libtevent0:armhf.
Preparing to unpack .../03-libtevent0_0.9.37-1_armhf.deb ...
Unpacking libtevent0:armhf (0.9.37-1) ...
Selecting previously unselected package libldb1:armhf.
Preparing to unpack .../04-libldb1_2%3a1.5.1+really1.4.6-3_armhf.deb ...
Unpacking libldb1:armhf (2:1.5.1+really1.4.6-3) ...
Selecting previously unselected package libpython2.7:armhf.
Preparing to unpack .../05-libpython2.7_2.7.16-2_armhf.deb ...
Unpacking libpython2.7:armhf (2.7.16-2) ...
Selecting previously unselected package python-ldb.
Preparing to unpack .../06-python-ldb_2%3a1.5.1+really1.4.6-3_armhf.deb ...
Unpacking python-ldb (2:1.5.1+really1.4.6-3) ...
Selecting previously unselected package python-tdb.
Preparing to unpack .../07-python-tdb_1.3.16-2+b1_armhf.deb ...
Unpacking python-tdb (1.3.16-2+b1) ...
Selecting previously unselected package libjansson4:armhf.
Preparing to unpack .../08-libjansson4_2.12-1_armhf.deb ...
Unpacking libjansson4:armhf (2.12-1) ...
Selecting previously unselected package python-talloc:armhf.
Preparing to unpack .../09-python-talloc_2.1.14-2_armhf.deb ...
Unpacking python-talloc:armhf (2.1.14-2) ...
Selecting previously unselected package samba-libs:armhf.
Preparing to unpack .../10-samba-libs_2%3a4.9.5+dfsg-5_armhf.deb ...
Unpacking samba-libs:armhf (2:4.9.5+dfsg-5) ...
Selecting previously unselected package python-samba.
Preparing to unpack .../11-python-samba_2%3a4.9.5+dfsg-5_armhf.deb ...
Unpacking python-samba (2:4.9.5+dfsg-5) ...
Selecting previously unselected package samba-common.
Preparing to unpack .../12-samba-common_2%3a4.9.5+dfsg-5_all.deb ...
Unpacking samba-common (2:4.9.5+dfsg-5) ...
Selecting previously unselected package samba-common-bin.
Preparing to unpack .../13-samba-common-bin_2%3a4.9.5+dfsg-5_armhf.deb ...
Unpacking samba-common-bin (2:4.9.5+dfsg-5) ...
Selecting previously unselected package tdb-tools.
Preparing to unpack .../14-tdb-tools_1.3.16-2+b1_armhf.deb ...
Unpacking tdb-tools (1.3.16-2+b1) ...
Selecting previously unselected package samba.
Preparing to unpack .../15-samba_2%3a4.9.5+dfsg-5_armhf.deb ...
Unpacking samba (2:4.9.5+dfsg-5) ...
Selecting previously unselected package attr.
Preparing to unpack .../16-attr_1%3a2.4.48-4_armhf.deb ...
Unpacking attr (1:2.4.48-4) ...
Selecting previously unselected package libibverbs1:armhf.
Preparing to unpack .../17-libibverbs1_22.1-1_armhf.deb ...
Unpacking libibverbs1:armhf (22.1-1) ...
Selecting previously unselected package ibverbs-providers:armhf.
Preparing to unpack .../18-ibverbs-providers_22.1-1_armhf.deb ...
Unpacking ibverbs-providers:armhf (22.1-1) ...
Selecting previously unselected package libboost-atomic1.67.0:armhf.
Preparing to unpack .../19-libboost-atomic1.67.0_1.67.0-13_armhf.deb ...
Unpacking libboost-atomic1.67.0:armhf (1.67.0-13) ...
Selecting previously unselected package libboost-iostreams1.67.0:armhf.
Preparing to unpack .../20-libboost-iostreams1.67.0_1.67.0-13_armhf.deb ...
Unpacking libboost-iostreams1.67.0:armhf (1.67.0-13) ...
Selecting previously unselected package libboost-regex1.67.0:armhf.
Preparing to unpack .../21-libboost-regex1.67.0_1.67.0-13_armhf.deb ...
Unpacking libboost-regex1.67.0:armhf (1.67.0-13) ...
Selecting previously unselected package libboost-system1.67.0:armhf.
Preparing to unpack .../22-libboost-system1.67.0_1.67.0-13_armhf.deb ...
Unpacking libboost-system1.67.0:armhf (1.67.0-13) ...
Selecting previously unselected package libboost-thread1.67.0:armhf.
Preparing to unpack .../23-libboost-thread1.67.0_1.67.0-13_armhf.deb ...
Unpacking libboost-thread1.67.0:armhf (1.67.0-13) ...
Selecting previously unselected package librados2:armhf.
Preparing to unpack .../24-librados2_12.2.11+dfsg1-2.1+rpi1_armhf.deb ...
Unpacking librados2:armhf (12.2.11+dfsg1-2.1+rpi1) ...
Selecting previously unselected package libcephfs2:armhf.
Preparing to unpack .../25-libcephfs2_12.2.11+dfsg1-2.1+rpi1_armhf.deb ...
Unpacking libcephfs2:armhf (12.2.11+dfsg1-2.1+rpi1) ...
Selecting previously unselected package libglusterfs0:armhf.
Preparing to unpack .../26-libglusterfs0_5.5-3_armhf.deb ...
Unpacking libglusterfs0:armhf (5.5-3) ...
Selecting previously unselected package libgfxdr0:armhf.
Preparing to unpack .../27-libgfxdr0_5.5-3_armhf.deb ...
Unpacking libgfxdr0:armhf (5.5-3) ...
Selecting previously unselected package libgfrpc0:armhf.
Preparing to unpack .../28-libgfrpc0_5.5-3_armhf.deb ...
Unpacking libgfrpc0:armhf (5.5-3) ...
Selecting previously unselected package libgfapi0:armhf.
Preparing to unpack .../29-libgfapi0_5.5-3_armhf.deb ...
Unpacking libgfapi0:armhf (5.5-3) ...
Selecting previously unselected package libgpgme11:armhf.
Preparing to unpack .../30-libgpgme11_1.12.0-6_armhf.deb ...
Unpacking libgpgme11:armhf (1.12.0-6) ...
Selecting previously unselected package python-gpg.
Preparing to unpack .../31-python-gpg_1.12.0-6_armhf.deb ...
Unpacking python-gpg (1.12.0-6) ...
Selecting previously unselected package samba-dsdb-modules:armhf.
Preparing to unpack .../32-samba-dsdb-modules_2%3a4.9.5+dfsg-5_armhf.deb ...
Unpacking samba-dsdb-modules:armhf (2:4.9.5+dfsg-5) ...
Selecting previously unselected package samba-vfs-modules:armhf.
Preparing to unpack .../33-samba-vfs-modules_2%3a4.9.5+dfsg-5_armhf.deb ...
Unpacking samba-vfs-modules:armhf (2:4.9.5+dfsg-5) ...
Setting up python-crypto (2.6.1-9+b1) ...
Setting up libibverbs1:armhf (22.1-1) ...
Setting up libpython2.7:armhf (2.7.16-2) ...
Setting up libboost-regex1.67.0:armhf (1.67.0-13) ...
Setting up ibverbs-providers:armhf (22.1-1) ...
Setting up attr (1:2.4.48-4) ...
Setting up libtdb1:armhf (1.3.16-2+b1) ...
Setting up samba-common (2:4.9.5+dfsg-5) ...
Creating config file /etc/samba/smb.conf with new version
Setting up libgpgme11:armhf (1.12.0-6) ...
Setting up libjansson4:armhf (2.12-1) ...
Setting up libglusterfs0:armhf (5.5-3) ...
Setting up libtevent0:armhf (0.9.37-1) ...
Setting up tdb-tools (1.3.16-2+b1) ...
update-alternatives: using /usr/bin/tdbbackup.tdbtools to provide /usr/bin/tdbbackup (tdbbackup) in auto mode
Setting up libboost-iostreams1.67.0:armhf (1.67.0-13) ...
Setting up python-tdb (1.3.16-2+b1) ...
Setting up libboost-atomic1.67.0:armhf (1.67.0-13) ...
Setting up python-dnspython (1.16.0-1) ...
Setting up libboost-system1.67.0:armhf (1.67.0-13) ...
Setting up python-gpg (1.12.0-6) ...
Setting up python-talloc:armhf (2.1.14-2) ...
Setting up libgfxdr0:armhf (5.5-3) ...
Setting up libldb1:armhf (2:1.5.1+really1.4.6-3) ...
Setting up libboost-thread1.67.0:armhf (1.67.0-13) ...
Setting up samba-libs:armhf (2:4.9.5+dfsg-5) ...
Setting up python-ldb (2:1.5.1+really1.4.6-3) ...
Setting up samba-dsdb-modules:armhf (2:4.9.5+dfsg-5) ...
Setting up libgfrpc0:armhf (5.5-3) ...
Setting up librados2:armhf (12.2.11+dfsg1-2.1+rpi1) ...
Setting up python-samba (2:4.9.5+dfsg-5) ...
Setting up samba-vfs-modules:armhf (2:4.9.5+dfsg-5) ...
Setting up libcephfs2:armhf (12.2.11+dfsg1-2.1+rpi1) ...
Setting up libgfapi0:armhf (5.5-3) ...
Setting up samba-common-bin (2:4.9.5+dfsg-5) ...
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE
Done
Setting up samba (2:4.9.5+dfsg-5) ...
Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-ad-dc.service masked)
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service.
Processing triggers for systemd (241-5+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
root@raspberrypi:~#
Also no service installed
Code: Select all
root@raspberrypi:~# service --status-all
[ - ] alsa-utils
[ + ] avahi-daemon
[ + ] bluetooth
[ - ] console-setup.sh
[ + ] cron
[ + ] dbus
[ + ] dhcpcd
[ + ] dphys-swapfile
[ + ] fake-hwclock
[ - ] hwclock.sh
[ - ] keyboard-setup.sh
[ + ] kmod
[ + ] networking
[ - ] nfs-common
[ + ] nmbd
[ + ] openhab2
[ - ] paxctld
[ + ] procps
[ + ] raspi-config
[ ? ] rng-tools
[ - ] rpcbind
[ - ] rsync
[ + ] rsyslog
[ - ] samba-ad-dc
[ + ] smbd
[ + ] ssh
[ - ] sudo
[ + ] triggerhappy
[ + ] udev
[ - ] x11-common
root@raspberrypi:~#
-
Crispin
- Posts: 8
- Joined: Thu Oct 18, 2012 11:59 pm
Re: RPi 4 — Samba installed but service won’t start
Sat Jun 29, 2019 5:34 am
fruitoftheloom wrote: ↑
Sat Jun 29, 2019 5:25 am
OpenJDK8 is not in the Buster repositories, it is OpenJDK11
Code: Select all
sudo apt update sudo apt full-upgrade sudo rebootCode: Select all
sudo apt update sudo apt install samba-common-bin
Hi,
It’s installed though —
Code: Select all
root@raspberrypi:~# update-alternatives --config java
There is only one alternative in link group java (providing /usr/bin/java): /usr/lib/jvm/java-8-openjdk-armhf/jre/bin/java
Nothing to configure.
Code: Select all
root@raspberrypi:~# java -version
openjdk version "1.8.0_212"
OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1+rpi1-b01)
OpenJDK Client VM (build 25.212-b01, mixed mode)
samba common is installed (auto-installed after purge)
Code: Select all
root@raspberrypi:~# apt install samba-common-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
samba-common-bin is already the newest version (2:4.9.5+dfsg-5).
samba-common-bin set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@raspberrypi:~#
-
fruitoftheloom
- Posts: 27225
- Joined: Tue Mar 25, 2014 12:40 pm
Re: RPi 4 — Samba installed but service won’t start
Sat Jun 29, 2019 5:59 am
i am running a fresh install of Buster fully updated
Code: Select all
java -version
openjdk version "11.0.3" 2019-04-16
OpenJDK Runtime Environment (build 11.0.3+7-post-Raspbian-5)
OpenJDK Server VM (build 11.0.3+7-post-Raspbian-5, mixed mode)
Samba 2:4.9.5+dfsg-5 plus dependencies………
Last edited by fruitoftheloom on Sat Jun 29, 2019 6:08 am, edited 1 time in total.
Take what I advise as advice not the utopian holy grail, and it is gratis !!
-
hortimech
- Posts: 714
- Joined: Wed Apr 08, 2015 5:52 pm
Re: RPi 4 — Samba installed but service won’t start
Sat Jun 29, 2019 7:28 am
You do have Samba installed, you are just mistaking the package name for the service names 
Code: Select all
root@raspberrypi:~# service --status-all
.........
[ + ] nmbd
.........
[ + ] smbd
.........
Are they actually running ?
Try restarting ‘smbd’ & ‘nmbd’
As for the ‘blog’ you followed, you might just as well not create a Samba user and use this share:
Code: Select all
[share]
Comment = Pi shared folder
Path = /share
read only = no
create mask = 0777
directory mask = 0777
Guest ok = yes
It will work just like the one in the blog, but with less lines.
You should also check that ‘map to guest = bad user’ is set in [global]
If ‘smbd’ & ‘nmbd’ are running, you should be able to connect to the share, but you will probably have to navigate to it, seeing as SMBv1 is now turned off.
-
Crispin
- Posts: 8
- Joined: Thu Oct 18, 2012 11:59 pm
Re: RPi 4 — Samba installed but service won’t start
Sat Jun 29, 2019 9:24 pm
well, yes and no.
So, it turns out it was working the whole time. I did not bother checking through windows if it is actually sharing them. When I did I face-palmed. 
On my RPi3B+ I see the following
Code: Select all
[ + ] raspi-config
[ - ] rpcbind
[ - ] rsync
[ + ] rsyslog
[ + ] samba
[ - ] samba-ad-dc
[ - ] screen-cleanup
[ + ] smbd
[ + ] ssh
[ - ] sudo
[ + ] triggerhappy
[ + ] udev
[ - ] ups-monitor
As you can see there is a service called samba and smdb. On the RPi4 there is only smbd.
I’m sure I am not the only one who is using the previously mentioned tutorial so hopefully this thread will help others.
Glad I am not going mad
Thanks for your help!
Return to “Troubleshooting”
Всем привет. Пытаюсь настроить сервер на основе Debian, и столкнулся с проблемой при настройке <Samba> выходит ошибка, < E: Sub-process /usr/bin/dpkg returned an error code (1)> вижу что неудолетворенные зависимости
ergei@debian:~$ sudo apt-get install -f
Мы полагаем, что ваш системный администратор изложил вам основы
безопасности. Как правило, всё сводится к трём следующим правилам:
№1) Уважайте частную жизнь других.
№2) Думайте, прежде что-то вводить.
№3) С большой властью приходит большая ответственность.
[sudo] пароль для cergei:
sudo: /var/lib/sudo/lectured is group writable
Чтение списков пакетов... Готово
Построение дерева зависимостей
Чтение информации о состоянии... Готово
Обновлено 0 пакетов, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 469 пакетов не обновлено.
Установлено или удалено не до конца 2 пакетов.
После данной операции объём занятого дискового пространства возрастёт на 0 B.
Настраивается пакет samba-common-bin (2:4.11.5+dfsg-1+b1) ...
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
Error loading services.
dpkg: ошибка при обработке пакета samba-common-bin (--configure):
installed samba-common-bin package post-installation script subprocess returned error exit status 1
dpkg: зависимости пакетов не позволяют настроить пакет samba:
samba зависит от samba-common-bin (= 2:4.11.5+dfsg-1+b1), однако:
Пакет samba-common-bin пока не настроен.
dpkg: ошибка при обработке пакета samba (--csudo apt-get update --fix-missing
sudo apt-get install -fonfigure):
проблемы зависимостей — оставляем не настроенным
При обработке следующих пакетов произошли ошибки:
samba-common-bin
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
и пытался все это исправить осноываясь на советах из интернета, полностью удалял весь пакет <samba> используя команды:
sudo apt-get update --fix-missing не помогло. Затем второй подход
sudo apt-get install -f
sudo dpkg --configure -a Опять мимо, ну и затем
sudo apt-get clean
sudo apt-get update
sudo apt-get remove sudo dpkg --remove --force-remove-reinstreq samba
sudo apt-get clean
sudo apt-get update
и заново устаналиаю пакет <samba> а потом все рано при обновлении пакетов выходит что ,<samba> и <samba-common-bin> с ошибкой как видно в выводе терминала.Чувствую что где то накосячил а вот где и как исправить не вникну. Вот ниже предсталяю данные системы на которой это все и разворачивается :
an:~$ uname -a
Linux debian 5.2.9-kirkwood-tld-1 #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019 armv5tel GNU/Linux
cergei@debian:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux bullseye/sid
Release: stable-updates
Codename: sid
cergei@debian:~$ cat /etc/apt/sources.list
deb http://deb.debian.org/debian buster main
deb-src http://deb.debian.org/debian buster main
deb http://deb.debian.org/debian-security/ buster/updates main
deb-src http://deb.debian.org/debian-security/ buster/updates main
deb http://deb.debian.org/debian buster-updates main
deb-src http://deb.debian.org/debian buster-updates main
deb http://ftp.ru.debian.org/debian sid main
cergei@debian:~$ ls /etc/apt/sources.list.d
ls: невозможно получить доступ к '/etc/apt/sources.list.d': Нет такого файла или каталога
Любые советы будут приняты с благодарностью.
Привёл пост в более удобночитаемый вид. Ogost
- Печать
Страницы: [1] Вниз
Тема: Samba error (Прочитано 1843 раз)
0 Пользователей и 1 Гость просматривают эту тему.
lcdboost
Всем здравствуйте. Помогите с самбой
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-11-18 11:57:59 MSK; 1min 14s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 6367 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Main PID: 6389 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 1978)
Memory: 19.2M
CGroup: /system.slice/smbd.service
├─6389 /usr/sbin/smbd --foreground --no-process-group
├─6391 /usr/sbin/smbd --foreground --no-process-group
├─6392 /usr/sbin/smbd --foreground --no-process-group
└─6393 /usr/sbin/smbd --foreground --no-process-group
ноя 18 11:57:58 father-A780LM-M2 systemd[1]: Stopped Samba SMB Daemon.
ноя 18 11:57:58 father-A780LM-M2 systemd[1]: Starting Samba SMB Daemon...
ноя 18 11:57:59 father-A780LM-M2 systemd[1]: Started Samba SMB Daemon.
ноя 18 11:57:59 father-A780LM-M2 smbd[6389]: [2020/11/18 11:57:59.742309, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
ноя 18 11:57:59 father-A780LM-M2 smbd[6389]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
как будто бы в активе но ресурсов не дает.
конфиг самбы
[global]при первичной установке работало всё. правда недолго:) os ubuntu-mate 20.04
workgroup = WORKGROUP
server string = Server Samba's
log file = /var/log/samba/samba.%m
max log size = 500
map to guest = Bad Password
prefered master = yes
local master = yes
os level = 65
[storage]
path = /storage
comment = Obmen
writable = yes
public = yes
create mask = 0777
directory mask = 0777
AlexDem
как будто бы в активе но ресурсов не дает
Потрудись описать проблему более корректно и полно. Что ты имел ввиду?
lcdboost
AlexDem, нет расшаренных каталогов
tagilchanin
testparm выполни и посмотри что скажет
Выбери профессию, которую ты любишь, — и тебе не придется работать ни дня в твоей жизни. (Конфуций)
lcdboost
testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
WARNING: The 'netbios name' is too long (max. 15 chars).
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
log file = /var/log/samba/samba.%m
map to guest = Bad Password
max log size = 500
os level = 65
preferred master = Yes
server string = Server Samba's
idmap config * : backend = tdb
[storage]
comment = Obmen
create mask = 0777
directory mask = 0777
guest ok = Yes
path = /storage
read only = No
father@father-A780LM-M2:~$ testparm >testparm.txt
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
WARNING: The 'netbios name' is too long (max. 15 chars).
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
AlexDem
нет расшаренных каталогов
smbstatusвыводит список расшаренных каталогов на сервере.
Должно быть как то так:
~# smbstatus
Samba version 4.3.11-Ubuntu
PID Username Group Machine Protocol Version
------------------------------------------------------------------------------
598 alex alex 10.100.0.22 (ipv4:10.100.0.22:49720) Unknown (0x0311)
Service pid machine Connected at
-------------------------------------------------------
Allusers 598 10.100.0.22 Wed Nov 18 12:58:05 2020
Restricted 598 10.100.0.22 Wed Nov 18 12:58:05 2020
Locked files:
Pid Uid DenyMode Access R/W Oplock SharePath Name Time
--------------------------------------------------------------------------------------------------
598 65534 DENY_ALL 0x100080 RDONLY NONE /samba/allusers . Wed Nov 18 13:38:31 2020
598 1003 DENY_ALL 0x100080 RDONLY NONE /samba/restricted . Wed Nov 18 13:38:31 2020
У тебя что говорит? Доступ к каталогам как настроен, по логину/паролю?
« Последнее редактирование: 18 Ноября 2020, 19:23:09 от AlexDem »
lcdboost
AlexDem,
Samba version 4.11.6-Ubuntu
PID Username Group Machine Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
Service pid Machine Connected at Encryption Signing
---------------------------------------------------------------------------------------------
No locked files
доступ к каталогу без пароля но права выдаю полные
сhmod 777 /storage
по конфигу smb.conf
...Выявил такую фигню, рестарт самбы помогает ненадолго.
map to guest = Bad Password
...
AlexDem
Попробуй добавить в секцию Storage
browsable = yes
А диски не видны только на одном девайсе, или на всех?
Кстати, у тебя еще ошибка появляется: WARNING: The ‘netbios name’ is too long (max. 15 chars).
Не уверен что с этим связана проблема, но погугли как решить.
« Последнее редактирование: 18 Ноября 2020, 20:58:41 от AlexDem »
lcdboost
AlexDem,
а разве он по умолчанию не включен?
добавил в конфиг browsable = yes, перезапустил сейчас смотрю надолго ли его хватит.
по ошибке в global добавил netbios name = UBUNTU ошибка ушла.
AlexDem
перезапустил сейчас смотрю надолго ли его хватит
После перезагрузки смонтируй расшаренную папку клиентом и выполни на сервере команду
smbstatusЕсли она не выводит список расшаренных папок, то это что-то странное, должны быть (см. мой вывод, там 2 папки видны).
Пользователь добавил сообщение 18 Ноября 2020, 22:53:28:
а разве он по умолчанию не включен?
включен, но дабы быть уверенным, что его ничего не переназначило
« Последнее редактирование: 18 Ноября 2020, 22:56:30 от AlexDem »
lcdboost
AlexDem,
smbstatus
sudo smbstatus
Samba version 4.11.6-Ubuntu
PID Username Group Machine Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
2636 nobody nogroup 192.168.1.4 (ipv4:192.168.1.4:40164) SMB3_02 - -
Service pid Machine Connected at Encryption Signing
---------------------------------------------------------------------------------------------
storage 2636 192.168.1.4 Чт ноя 19 09:44:18 2020 MSK - -
Locked files:
Pid User(ID) DenyMode Access R/W Oplock SharePath Name Time
--------------------------------------------------------------------------------------------------
2636 65534 DENY_NONE 0x89 RDONLY NONE /storage serials/[video_name.mp4] Thu Nov 19 09:44:18 2020
Проверяю с помощью vlc на андроиде. Простой вход в расшаренную папку не показыватся в статусе. При воспроизведении медиа лог есть.
AlexDem
Проверяю с помощью vlc
Да вроде нормально у тебя все работает. У тебя протокол 3.02, посмотри чтобы на всех клиентах был минимум этот протокол. Если нет заморочек с безопасностью, то я бы поставил 2.0 минимум на сервере.
« Последнее редактирование: 19 Ноября 2020, 10:07:59 от AlexDem »
lcdboost
AlexDem, спасибо за помощь, а как сменить протокол?
AlexDem
lcdboost
- Печать
Страницы: [1] Вверх