You are not logged in.

#1 2017-10-28 11:07:59

firekage
Member
From: Eastern Europe, Poland
Registered: 2013-06-30
Posts: 617

[SOLVED] Cant enter samba shares - no workgroup in Samba

Hi.

I would like to ask for your help. I dont know what i could do much to solve my problem. I just cant enter samba shares via KDE/Dolphin.

This is log from terminal

2017/10/28 13:04:15.464407,  0] ../lib/util/debug.c:1053(reopen_logs_internal)
  Unable to open new log file '/usr/local/samba/var/log.%m': No such file or directory
[2017/10/28 13:04:15.464454,  0] ../source4/smbd/server.c:428(binary_smbd_main)
  samba version 4.7.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2017

I start Dolphin > Samba Shares >  and in "nSamba Shares" should be at last my home folder or my shares. There is no single one. Folder of my arch is being shown only when i enter ip address of my machine into Dolphin bar, but even when i try to access it, i just cant. I got error about "unknown error in stat file, report bug to KDE".

I have this in my setup of samba:

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba, 
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the 
# Samba-Guide which is generated daily and can be downloaded from: 
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash) 
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors. 
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Samba Server
   netbios name = 7500_uATX

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.
    hosts allow = 192.168.0. 192.168.1. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /usr/local/samba/var/log.%m

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Specifies the Kerberos or Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes
    wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#	Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 

# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g


#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = no
   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /usr/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = no
;   printable = no
;   write list = @staff

# Other examples. 
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

[7500_uATX]
comment = 7500_uATX
path = /mnt/
valid users = firekage
public = no
writeable = yes
printable = no
browseable = yes
valid users = firekage
write list = firekage

i have this in /etc/hosts:

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1	localhost.localdomain	localhost
#::1		localhost.localdomain	localhost
192.168.0.110   7500_uATX
# End of file

and this in /etc/nsswitch.conf


# Begin /etc/nsswitch.conf

passwd: compat mymachines systemd
group: compat mymachines systemd
shadow: compat

publickey: files

hosts: files mymachines resolve [!UNAVAIL=return] dns wins myhostname
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

# End /etc/nsswitch.conf

Could somebody help?


Forget about this:

[firekage@7500_uATX ~]$ smbtree
WORKGROUP
        \\7500_UATX                     Samba Server
                \\7500_UATX\IPC$                IPC Service (Samba Server)
                \\7500_UATX\7500_uATX           7500_uATX
[firekage@7500_uATX ~]$ smbclient -L firekage
Connection to firekage failed (Error NT_STATUS_UNSUCCESSFUL)
[firekage@7500_uATX ~]$ smbclient -L 7500_uATX
Enter WORKGROUP\firekage's password: 

        Sharename       Type      Comment
        ---------       ----      -------
        7500_uATX       Disk      7500_uATX
        IPC$            IPC       IPC Service (Samba Server)
        firekage        Disk      Home Directories
Reconnecting with SMB1 for workgroup listing.

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        WORKGROUP            7500_UATX

Last edited by firekage (2017-10-29 12:41:55)

Offline

#2 2017-10-29 12:39:56

firekage
Member
From: Eastern Europe, Poland
Registered: 2013-06-30
Posts: 617

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

Ok. I now know perfectly that is was not Samba issue, not my samba config issue...but...again, something wrong with updates, linux, KDE, or Dolphin. I've been trying to solve it past several days, wasting time...because i was digging in Samba, Samba configuration. my usershares and network configuration.

This was something that solved my problem:

https://forum.manjaro.org/t/solved-cannot-browse-samba-shares-after-update/32955/4

It should be in KDE section, Dolphin section or even Arch Samba section!


Here, what is important:

In 

 [global] 

section of smb.conf there should be placed this:

client max protocol = NT1

...Why something like this is not mentioned, explained but solution should be searched everywhere? What is most funny, i made topic on Arch site, while when somebody ask about Manjaro, here, topic is closed! Strange. Strange is something more - i had to use it from last updated. Never used this earlier!

Last edited by firekage (2017-10-29 12:41:35)

Offline

#3 2017-10-29 13:10:07

seth
Member
Registered: 2012-09-03
Posts: 49,963

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

You're quite late to the party ...
https://bbs.archlinux.org/viewtopic.php?id=230470
https://bbs.archlinux.org/viewtopic.php?id=230979
https://bbs.archlinux.org/viewtopic.php?id=230660

This is actually all over the place in different variants. The cause is that upstream switched the default protocol because SMBv1 had recently rather bad press...

The correct solution is btw. to NOT use dolphin kio-cifs, https://bugs.kde.org/show_bug.cgi?id=339752
I'm not sure about the claimed upstream fix, but a general issue will be that the higher protocol versions do not provide posix extensions, iow: stop using SMB, it's a crap protocol to begin with (and this is btw. also stance of the SAMBA developers - SAMBA exists because SMB is significant, not because it's a good choice)

Online

#4 2017-12-05 07:13:10

firekage
Member
From: Eastern Europe, Poland
Registered: 2013-06-30
Posts: 617

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

Don't understand. Stop using SMB, so use what? There is nothing more that does this kind of job, right?

Last edited by firekage (2017-12-05 07:13:34)

Offline

#5 2017-12-05 08:28:16

seth
Member
Registered: 2012-09-03
Posts: 49,963

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

What is "this kind of job"?
If you're spellbound to windows, then the answer is (for the moment): "not reasonably".
Otherwise smb is redundant in it's function as remote filesystem or printer sharing protocol as well as RPC (if you actually want to buy into this)

In a pure POSIX environment, SMB is about the worst choice for every job it does.

Online

#6 2017-12-05 08:35:56

firekage
Member
From: Eastern Europe, Poland
Registered: 2013-06-30
Posts: 617

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

So in other word, if i want to browse my shares under Arch, and using of Samba is a wrong choice, than is there any other choice? I always knew that it is only SMB for linux file sharing across computers.

Offline

#7 2017-12-05 08:41:00

seth
Member
Registered: 2012-09-03
Posts: 49,963

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

if i want to browse my shares

What "shares"? If you want to access windows shares, using NFS et al. under windows is still rather a PITA. If you don't have a windows system in your network, "man nfs", if your connection is unreliable (because you shutdown systems etc) also have a brief look at https://unix.stackexchange.com/question … -directory

Online

#8 2018-03-24 17:34:12

gearhead
Member
Registered: 2018-03-24
Posts: 56

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

Firekage, thanks for the suggestion of using:
client max protocol = NT1
in the global section. I was banging my head aginst the wall on this. Share browsing works on my ubuntu machines but not arch. Now it does.

Second, please quit bashing samba. Even in a pure linux environment (like mine) it is still needed and up to date docs are required. There are many IoT devices which use only samba.

Gearhead

Last edited by gearhead (2018-03-24 17:39:38)

Offline

#9 2018-03-24 17:42:28

seth
Member
Registered: 2012-09-03
Posts: 49,963

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

It's requirement does certainly not relate to its quality (or lack thereof) - and questioning the latter isn't "bashing".

Please also notice that setting the max protocol to NT1 is a terrible "solution"
NT1 was ditched because of the inherent security flaws that caused the wannacry et al. situation. You should not use it and you should certainly not enforce its usage.

Online

#10 2018-03-24 17:57:24

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [SOLVED] Cant enter samba shares - no workgroup in Samba

gearhead wrote:

Even in a pure linux environment (like mine) it is still needed

I'd be interested to know why it's still needed. What does it do that can't be achieved with native Linux software?


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

Board footer

Powered by FluxBB