You are not logged in.

#1 2017-11-12 11:29:55

piedro
Member
Registered: 2013-04-11
Posts: 179

Samba usershares can't be accessed - they are found then time out

Hi!

After resolving usershare problems with the nautilus shares in gnome 3.26 I ran into this issue which I cannot find any solution for:


My arch box can access the shares I created with nautilus.
No virtualbox nor other network box can access them.

Any client sees the network shares in the correct workgroup, also finds all the shares on the server (my arch box) but if trying to open the shared folder there is an immediate "folder timed out" error.

Now there is the hint in the arch wiki to correct the line

name resolve order = lmhosts wins hosts bcast
with
name resolve order = lmhosts bcast host

which I did.

Tried in smb.conf
client max protocol = NT1

didn't work

Different virtual boxes with (also external boxes) can browse the network and see every share but can't enter the shared folder.  I tried running winbindd in addition and I tried without it... do I need it?

Strange thing is information is really scarce here - samba 4.7 should be broken on arch (?) but what about 4.7.1?
Also 4.7 is really old and I cannot believe that it is still broken...

There is the possibility of creating system wide samba shares and then create fixed network locations within the clients but that is not what I need: we need the adhoc sharing (virtualboxes mainly for testing at the moment).

here is the result of testparm:

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
	dns proxy = No
	log file = /var/log/samba/log.%m
	max log size = 50
	name resolve order = lmhosts bcast host
	server role = standalone server
	server string = Arch Server
	usershare allow guests = Yes
	usershare max shares = 100
	usershare path = /var/lib/samba/usershare
	workgroup = UR
	idmap config * : backend = tdb
	hosts allow = 192.168.10. 127.

[homes]
	browseable = No
	comment = Home Directories
	read only = No

[printers]
	browseable = No
	comment = All Printers
	path = /usr/spool/samba
	printable = Yes

BTW, samba works fine on the NAS (browsable as expected, it's only the ARCH box which isn't working.


I would really appreciate some help here.

thx, p.

Offline

#2 2017-11-12 13:37:35

seth
Member
Registered: 2012-09-03
Posts: 6,557

Re: Samba usershares can't be accessed - they are found then time out

client max protocol = NT1

doesn't show up in your config. Previous posts suggested that a reboot is mandatory after this change (no idea what service actually needs to be restarted) and it'S the by far most likely reason for this. Also posts about broken SMB were all over the place, most of them moved to dustbin because it was the same thing over and over and over again.

Offline

#3 2017-11-12 15:06:40

piedro
Member
Registered: 2013-04-11
Posts: 179

Re: Samba usershares can't be accessed - they are found then time out

Hmm, I will try once more with rebooting...

The missing entry, I tried with this setting and it hasn't worked, so I took it out again because I fsaw other posts saying that this entry messed things up even more...

About the dustbinned posts, what are you saying?

If someone's depending on basic network sharing functionality he/she has to jump ship and install another distro? Or even Windows? I mean what's the perspective here?

Is there at least a  known working version of samba?
Or don't we even know samba is the culprit?

Could we have a pinned thread for samba problems and solutions, please?
I think one of the main problems is that you can't really search for the problems cause the key words alway happen to be in any problem....

But thx for your clarification,
sad, p.

Last edited by piedro (2017-11-12 15:07:22)

Offline

#4 2017-11-12 15:23:46

piedro
Member
Registered: 2013-04-11
Posts: 179

Re: Samba usershares can't be accessed - they are found then time out

By reading the wiki again and again I stumbled over this line here:

"If you want to share paths inside your home directory you must make it listable for the group others"

How to do that without messing up the user permissions?
Isn't a user's group "users" or as default the same as the username?


I feel like fishing ...
p.

Offline

#5 2017-11-12 15:40:18

seth
Member
Registered: 2012-09-03
Posts: 6,557

Re: Samba usershares can't be accessed - they are found then time out

The perspective is that you'll have to review your entire SMB stack in your entire network because SMBv1 is now considered a severe security issue, SMBv2.x will be soon enough and v2 and v3 don't provide the posix extensions which many GUI tools rely on.

And of course the smb daemon must be able to access the shared paths, this is and has always been a requirement for any process in any OS.

About dustbin, see eg. https://bbs.archlinux.org/viewtopic.php?id=230746 https://bbs.archlinux.org/viewtopic.php?id=231106 and https://bbs.archlinux.org/viewtopic.php?id=231190 (you can click yourself through the dustbin for more threads on this)
This affects every distro which ships a recent version of samba and the situation on windows is the same (minus the posix extension trouble, obviously)

Offline

#6 2017-11-13 09:31:01

Elizine
Member
From: United Kingdom
Registered: 2015-10-07
Posts: 39
Website

Re: Samba usershares can't be accessed - they are found then time out

Try disabling your firewall, "service ipchains stop"

If that fixes it, you need to use redhat-config-securitylevel or
manual editing to punch your firewall for smb support.

Offline

Board footer

Powered by FluxBB