You are not logged in.
Pages: 1
Is there a way to share files through wifi, if so by GUI? I used to use samba back on ubuntu and it was really easy to setup and connect, but on Arch I can't make it work at all, I don't know if the commands I'm using are confusing (some say to start the service smbd others only smb, for example), if samba is not supposed to work on Arch for some reason, if I'm being stupid(that's probably it). I tried looking for it on the wiki, followed all the steps but it still refuses to work no matter what.
https://wiki.archlinux.org/title/samba
The same thing goes for vsftp
https://wiki.archlinux.org/title/Very_Secure_FTP_Daemon
I setup, edit the config file so I can login, it shows connection denied no matter what.... my config files for both are down here
Samba
[Public]
comment = public share
path = /home/rafael/Downloads
browseable = yes
writable = yes
guest ok = yes
vsftpd
# Example config file /etc/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
# Allow anonymous FTP? (Beware - allowed by default if you comment this out).
#anonymous_enable=YES
#
# Uncomment this to allow local users to log in.
#local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# chroot)
#chroot_local_user=YES
#chroot_list_enable=YES
# (default follows)
#chroot_list_file=/etc/vsftpd.chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
listen=YES
#
# This directive enables listening on IPv6 sockets. To listen on IPv4 and IPv6
# sockets, you must run two copies of vsftpd with two configuration files.
# Make sure, that one of the listen options is commented !!
#listen_ipv6=YES
# Set own PAM service name to detect authentication settings specified
# for vsftpd by the system package.
pam_service_name=vsftpd
Thanks in advance!
Offline
For each of these, what is the output of the following commands?
systemctl status smb.service
systemctl status vsftpd.serviceIt sounds very much like you've forgotten to run either of these commands:
sudo systemctl enable --now smb.service
sudo systemctl enable --now vsftpd.serviceUbuntu is terrible, in that it automatically enables and starts these services before you've had a chance to configure them. Arch is not like that; every service Arch Wiki article has the instruction to start/enable the service. This instruction is so pervasive throughout the Wiki it's easy to miss if you don't know you need to do it.
Offline
For each of these, what is the output of the following commands?
systemctl status smb.service systemctl status vsftpd.serviceIt sounds very much like you've forgotten to run either of these commands:
sudo systemctl enable --now smb.service sudo systemctl enable --now vsftpd.serviceUbuntu is terrible, in that it automatically enables and starts these services before you've had a chance to configure them. Arch is not like that; every service Arch Wiki article has the instruction to start/enable the service. This instruction is so pervasive throughout the Wiki it's easy to miss if you don't know you need to do it.
Thank you for your answer! I did use these commands, but I still get bugs when I try to access both, samba give me
NT_STATUS_BAD_NETWORK_NAME
and vsftp gives me
access denied
Even though both are supposed to accept anonymous logins, according to their config files.
But I used the status commands you said for both, here are the outputs:
systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.servi
ce; disabled; preset: disabled)
Active: active (running) since Fri 2024-02-16 18:01:22 -03; 16h ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 287521 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 3 (limit: 17881)
Memory: 8.6M (peak: 37.1M)
CPU: 2.148s
CGroup: /system.slice/smb.service
├─287521 /usr/bin/smbd --foreground --no-process-group
├─287525 "smbd: notifyd "
└─287526 "smbd: cleanupd"
Feb 16 18:24:54 archlinux rpcd_winreg[289390]: Copyright Andrew Tridgell and the Sa
mba Team 1992-2023
Feb 16 18:26:13 archlinux samba-dcerpcd[289463]: [2024/02/16 18:26:13.818422, 0] ../
../source3/rpc_server/rpc_host.c:2843(main)
Feb 16 18:26:13 archlinux samba-dcerpcd[289463]: samba-dcerpcd version 4.19.4 start
ed.
Feb 16 18:26:13 archlinux samba-dcerpcd[289463]: Copyright Andrew Tridgell and the Samba Team 1992-2023
Feb 16 18:26:13 archlinux rpcd_classic[289472]: [2024/02/16 18:26:13.945895, 0] ../../source3/rpc_server/rpc_worker.c:1127(rpc_worker_main)
Feb 16 18:26:13 archlinux rpcd_classic[289472]: rpcd_classic version 4.19.4 started.
Feb 16 18:26:13 archlinux rpcd_classic[289472]: Copyright Andrew Tridgell and the Samba Team 1992-2023
Feb 16 18:26:13 archlinux rpcd_winreg[289474]: [2024/02/16 18:26:13.987660, 0] ../../source3/rpc_server/rpc_worker.c:1127(rpc_worker_main)
Feb 16 18:26:13 archlinux rpcd_winreg[289474]: rpcd_winreg version 4.19.4 started.
Feb 16 18:26:13 archlinux rpcd_winreg[289474]: Copyright Andrew Tridgell and the Samba Team 1992-2023
systemctl status vsftpd.service
● vsftpd.service - vsftpd daemon
Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; disabled; preset:
disabled)
Active: active (running) since Fri 2024-02-16 18:58:22 -03; 15h ago
Main PID: 309019 (vsftpd)
Tasks: 1 (limit: 17881)
Memory: 712.0K (peak: 1.2M)
CPU: 28ms
CGroup: /system.slice/vsftpd.service
└─309019 /usr/bin/vsftpd
Feb 16 18:58:22 archlinux systemd[1]: Started vsftpd daemon.
Thank you again!
Offline
OK, don't forget to use code blocks to properly format your output and file snippets (see the BBCode link at the bottom of every forum input box).
What are the commands you're using to access these samba/vsftp shares? I'd try from the terminal to make sure that piece is working before you move onto the GUI tools. Follow the respective wiki articles for setting up and using the clients.
For Samba, try with smbclient, make sure the share is visible with smbclient -L. I've never used vsftp so I can be of little help using it.
Offline
Pages: 1