Yet another Samba problem
Hello. I'm trying to guest share a couple of folders but I've run into a problem I can't diagnose.
I've already run the recommended grep -E and tee and usermod commands. I've enabled the smb and nmb services and made sure they're running. (This caused the server to appear on the device I'm trying to connect with, so it is announcing.)
And I've run the recommended setsebool command.
The problem is when I try to connect to the server, it just times out. No error message. Nothing in the server's logs.
I've checked netstat and everything seems to be in order.
I'm stumped. This didn't happen on Mint or Debian, and I have no leads to follow. Any ideas?
13 Replies
Just to confirm: You have made firewall exceptions for samba on both devices?
outgoing is not blocked by default, but incoming is
otherwise i smell an SELinux issue
also make sure to edit the config to allow guest access
I was unable to locate any firewall settings in Bazzite, and the client is a mobile app which is able to connect to Samba servers running in other distros on the same machine as Bazzite.
I did try adding the guest access argument, but it had no effect. Notably I'm not getting an authorization refusal message like I normally do when guest access is the problem.
bazzite uses firewalld
same as fedora upstream
I thought the setsebool command was supposed to fix this.
Solution
Try this
No GUI config in Plasma, eh?
change the zone to whatever the active zone is
i believe there is no gui tool by default no
IIRC
wait let me check
The only result from searching "firewall" in the System Settings UI was Proxy, so I stupidly assumed the firewall wasn't a problem.
if its just a client connecting to a samba share then u dont need working incomign ports
incoming*
its wherever the share is located that requires the allowed incoming tcp and udp ports
this is because the firewall only blocks incoming connections by default, not outgoing
but connection timing out is in my experience almost always some issue with port access
(and SELinux of course)
Huzzah! That did it! Not even another issue behind that one, it's just fully working now! Thank you!
Awesome 🙂
💜