dolphin cannot access to smb://server@192.168.204.86/

pier_andreit · October 29, 2019, 3:02pm

on my TUXEDO InfinityBook Pro 15 v4 with 2Tb ssd disk, 58Gb /home EXT3 partition, 32Gb RAM,
processor= Intel Core i7-8565U, RAM=32Gb, 2TB SSD disk
dolphin cannot access to smb://server@192.168.204.86/
dolphin version=Version 19.08.2 plasma=5.17.0
the error is Timeout on server
192.168.204.86
network is ok

with another laptop on the same network but with leap 15.1 dolphin version=Version 19.08.2 plasma=5.17.0 I can easily access
how can I have the same access to smb ??

here is my repo list

pla@pla4-TW:~> zypper lr -u
Repository priorities in effect:                                                                                                      (See 'zypper lr -P' for details)
      90 (raised priority)  :  2 repositories
      93 (raised priority)  :  1 repository  
      99 (default priority) :  4 repositories

#  | Alias                                  | Name                 | Enabled | GPG Check | Refresh | URI                                                                       
---+----------------------------------------+----------------------+---------+-----------+---------+---------------------------------------------------------------------------
 1 | openSUSE_Tumbleweed                    | TUXEDO TW            | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/repositories/isv:/TUXEDO/openSUSE_Tumbleweed/
 2 | opensuse-guide.org-openSUSE_Tumbleweed | libdvdcss repository | No      | ----      | ----    | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/                       
 3 | packman.inode.at-openSUSE_Tumbleweed   | Packman Repository   | Yes     | (r ) Yes  | Yes     | http://packman.inode.at/suse/openSUSE_Tumbleweed/                         
 4 | repo-debug                             | repo-debug           | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/tumbleweed/repo/debug                        
 5 | repo-non-oss                           | repo-non-oss         | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/tumbleweed/repo/non-oss                      
 6 | repo-oss                               | repo-oss             | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/tumbleweed/repo/oss                          
 7 | repo-src-non-oss                       | repo-src-non-oss     | No      | ----      | ----    | http://download.opensuse.org/tumbleweed/repo/src-non-oss                  
 8 | repo-src-os                            | repo-src-os          | No      | ----      | ----    | http://download.opensuse.org/tumbleweed/repo/src-oss                      
 9 | repo-update                            | repo-update          | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/tumbleweed/                           
10 | x86_64                                 | google(chrome)       | Yes     | (r ) Yes  | Yes     | http://dl.google.com/linux/chrome/rpm/stable/x86_64                       
pla@pla4-TW:~>

knurpht · October 29, 2019, 3:08pm

Hey, welcome to the Tubleweed world !!!

Did you try without firewall ?

pier_andreit · October 29, 2019, 3:33pm

Hi manythanks

just checked, firewall is inactive
in tumbleweed dolphin can connect without problem with sftp://something but not with smb://192.168.204.86

deano_ferrari · October 29, 2019, 8:10pm

Is samba running?

sudo systemctl status smb

pier_andreit · October 30, 2019, 12:26pm

no, it wasnt, I started and enabled, rebooted but the error is the same, perhaps have I enable also nmb?

pla@pla4-TW:~> sudo systemctl status smb
[sudo] password for root: 
● smb.service - Samba SMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
pla@pla4-TW:~> sudo systemctl start smb
pla@pla4-TW:~> sudo systemctl status smb
● smb.service - Samba SMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: disabled)
   Active: active (running) since Wed 2019-10-30 12:07:32 CET; 5s ago
  Process: 17627 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
 Main PID: 17650 (smbd)
   Status: "smbd: ready to serve connections..."
    Tasks: 4 (limit: 4915)
   Memory: 31.5M
   CGroup: /system.slice/smb.service
           ├─17650 /usr/sbin/smbd --foreground --no-process-group
           ├─17652 /usr/sbin/smbd --foreground --no-process-group
           ├─17653 /usr/sbin/smbd --foreground --no-process-group
           └─17654 /usr/sbin/smbd --foreground --no-process-group

ott 30 12:07:31 pla4-TW.homenet.telecomitalia.it systemd[1]: Starting Samba SMB Daemon...
ott 30 12:07:31 pla4-TW.homenet.telecomitalia.it update-apparmor-samba-profile[17627]: Reloading updated AppArmor profile for Samba...
ott 30 12:07:32 pla4-TW.homenet.telecomitalia.it smbd[17650]: [2019/10/30 12:07:32.302493,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
ott 30 12:07:32 pla4-TW.homenet.telecomitalia.it smbd[17650]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
ott 30 12:07:32 pla4-TW.homenet.telecomitalia.it systemd[1]: Started Samba SMB Daemon.

deano_ferrari · October 30, 2019, 12:48pm

Any differences with the smb.conf configurations between working and non-working laptops?

malcolmlewis · October 30, 2019, 1:27pm

Hi
Have you checked the SMB version on the remote system? Likely SMB v1 which is deprecated…

pier_andreit · October 30, 2019, 1:35pm

no differences, this is the /etc/samba/smb.conf of both laptops

# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[global]
    workgroup = WORKGROUP
    passdb backend = tdbsam
    printing = cups
    printcap name = cups
    printcap cache time = 750
    cups options = raw
    map to guest = Bad User
    logon path = \\%L\profiles\.msprofile
    logon home = \\%L\%U\.9xprofile
    logon drive = P:
    usershare allow guests = Yes
[homes]
    comment = Home Directories
    valid users = %S, %D%w%S
    browseable = No
    read only = No
    inherit acls = Yes
[profiles]
    comment = Network Profiles Service
    path = %H
    read only = No
    store dos attributes = Yes
    create mask = 0600
    directory mask = 0700
[users]
    comment = All users
    path = /home
    read only = No
    inherit acls = Yes
    veto files = /aquota.user/groups/shares/
[groups]
    comment = All groups
    path = /home/groups
    read only = No
    inherit acls = Yes
[printers]
    comment = All Printers
    path = /var/tmp
    printable = Yes
    create mask = 0600
    browseable = No
[print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    write list = @ntadmin root
    force group = ntadmin
    create mask = 0664
    directory mask = 0775

pier_andreit · October 30, 2019, 1:37pm

how can I check this?
I suppose the remote system is a windows server but I don’t know more

deano_ferrari · October 30, 2019, 7:30pm

I would have expected that to have impacted the openSUSE Leap 15.1 host as well and the OP mentioned that it is working.

deano_ferrari · October 30, 2019, 7:50pm

What happens if you try something like

smbclient -m smb2 -L 192.168.204.86 -d 3

pier_andreit · October 31, 2019, 1:45pm

in the tumbleweed non working system happen this:

pla@pla4-TW:~> smbclient -m smb2 -L 192.168.204.86 -d 3
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
directory_create_or_exist_strict: invalid ownership on directory /var/lib/samba/lock/msg.lock
cmdline_messaging_context: Unable to initialize messaging context.
Unable to initialize messaging context
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
added interface wlan0 ip=192.168.219.193 bcast=192.168.219.255 netmask=255.255.255.0
Client started (version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64).
Connecting to 192.168.204.86 at port 445
protocol negotiation failed: NT_STATUS_IO_TIMEOUT
pla@pla4-TW:~>

in the leap 15.1 working system happen this:

iner@LE6-SABC-hw:~> smbclient -m smb2 -L 192.168.204.86 -d 3              
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
directory_create_or_exist_strict: invalid ownership on directory /var/lib/samba/lock/msg.lock
cmdline_messaging_context: Unable to initialize messaging context.
Unable to initialize messaging context
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
added interface wlan0 ip=192.168.219.162 bcast=192.168.219.255 netmask=255.255.255.0
Client started (version 4.9.5-git.187.71edee57d5alp151.2.6.1-SUSE-oS15.0-x86_64).
Connecting to 192.168.204.86 at port 445
Enter WORKGROUP\iner's password: 
GENSEC backend 'gssapi_spnego' registered
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'spnego' registered
GENSEC backend 'schannel' registered
GENSEC backend 'naclrpc_as_system' registered
GENSEC backend 'sasl-EXTERNAL' registered
GENSEC backend 'ntlmssp' registered
GENSEC backend 'ntlmssp_resume_ccache' registered
GENSEC backend 'http_basic' registered
GENSEC backend 'http_ntlm' registered
GENSEC backend 'http_negotiate' registered
Cannot do GSE to an IP address
Got challenge flags:
Got NTLMSSP neg_flags=0x628a8215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x62088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62088215
SPNEGO login failed: The attempted logon is invalid. This is either due to a bad username or authentication information.
Got challenge flags:
Got NTLMSSP neg_flags=0x628a8215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x62008a15
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62008a15
SPNEGO login failed: An invalid parameter was passed to a service or function.
session setup failed: NT_STATUS_INVALID_PARAMETER
iner@LE6-SABC-hw:~>

but I noted that smbclient ask me the “Enter WORKGROUP\iner’s password:”, iner is the linux local user, that is not the 192.168.204.86’s username (that is server) so I red the ****ing smbclient manual lol! and inserted the username, and happened this: (in the tumbleweed non working system happened the same thing as without the username)

iner@LE6-SABC-hw:~> smbclient -m smb2 --user=server -L 192.168.204.86 -d 3
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
directory_create_or_exist_strict: invalid ownership on directory /var/lib/samba/lock/msg.lock
cmdline_messaging_context: Unable to initialize messaging context.
Unable to initialize messaging context
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
added interface wlan0 ip=192.168.219.162 bcast=192.168.219.255 netmask=255.255.255.0
Client started (version 4.9.5-git.187.71edee57d5alp151.2.6.1-SUSE-oS15.0-x86_64).
Connecting to 192.168.204.86 at port 445
Enter WORKGROUP\server's password: 
GENSEC backend 'gssapi_spnego' registered
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'spnego' registered
GENSEC backend 'schannel' registered
GENSEC backend 'naclrpc_as_system' registered
GENSEC backend 'sasl-EXTERNAL' registered
GENSEC backend 'ntlmssp' registered
GENSEC backend 'ntlmssp_resume_ccache' registered
GENSEC backend 'http_basic' registered
GENSEC backend 'http_ntlm' registered
GENSEC backend 'http_negotiate' registered
Cannot do GSE to an IP address
Got challenge flags:
Got NTLMSSP neg_flags=0x628a8215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x62088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62088215

        Sharename       Type      Comment
        ---------       ----      -------
        J$              Disk      Condivisione predefinita
        R$              Disk      Condivisione predefinita
        DROPBOX B 60Gb  Disk      
        MUSICA 2        Disk      
        _ARCHIVIO _2018 Disk      
        C$              Disk      Condivisione predefinita
        K$              Disk      Condivisione predefinita
        GIOCHI          Disk      
        FILM NUOVI      Disk      
        DROPBOX PROGRAMMI Disk      
        MUSICA 1        Disk      
        H$              Disk      Condivisione predefinita
        P$              Disk      Condivisione predefinita
        DROPBOX A 400Gb Disk      
        _ARCHIVIO_2017  Disk      
        _ARCHIVIO_2016  Disk      
        I$              Disk      Condivisione predefinita
        FILM CARTONI    Disk      
        Raccolte Film   Disk      
        CONDIVIDERE FILE IN CARTELLE DROPBOX Disk      
        F$              Disk      Condivisione predefinita
        N$              Disk      Condivisione predefinita
        SERIE TV 1      Disk      
        IPC$            IPC       IPC remoto
        BIBLIOTECA TECNICA Disk      
        ADMIN$          Disk      Amministrazione remota
        PROGRAMMI       Disk      
        SERIE TV 2      Disk      
        L$              Disk      Condivisione predefinita
        E$              Disk      Condivisione predefinita
        ADMIN           Disk      
Reconnecting with SMB1 for workgroup listing.
Connecting to 192.168.204.86 at port 139
Connecting to 192.168.204.86 at port 139
Cannot do GSE to an IP address
Got challenge flags:
Got NTLMSSP neg_flags=0x628a8215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x62088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x62088215

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

        Workgroup            Master
        ---------            -------
iner@LE6-SABC-hw:~>

deano_ferrari · October 31, 2019, 6:05pm

That looks better.

pier_andreit · November 2, 2019, 12:33pm

:sarcastic: not so better, the non working tumbleweed system continues to not work and the working leap 5.1 system continues to work.
but there is an evolution if it helps, at home, where I have a samba domestic server on an leap 15,1 server the tumbleweed non working system works, it seems that the tumbleweed doesn’t accept the server server@192.168.204.86 I suppose a windows server.

deano_ferrari · November 2, 2019, 9:30pm

Good

it seems that the tumbleweed doesn’t accept the server server@192.168.204.86 I suppose a windows server.

This is a windows server in another environment (eg workplace) that you need to connect to? Do you have the appropriate credentials to do so?

pier_andreit · November 4, 2019, 9:57am

yes, I have the appropriate credentials, I used with the leap 15.1 working system that with sambaclient that asked me the password

Connecting to 192.168.204.86 at port 445 
Enter WORKGROUP\server's password:

where the non working tumbleweed system doesn’t

Connecting to 192.168.204.86 at port 445
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

deano_ferrari · November 4, 2019, 7:12pm

pier_andreit:

yes, I have the appropriate credentials, I used with the leap 15.1 working system that with sambaclient that asked me the password
Connecting to 192.168.204.86 at port 445 
Enter WORKGROUP\server's password: 
where the non working tumbleweed system doesn’t
Connecting to 192.168.204.86 at port 445
protocol negotiation failed: NT_STATUS_IO_TIMEOUT

You mentioned earlier that the client firewall is inactvie, but can you confirm that with

firewall-cmd --state

firewall-cmd --list-services

You might also need some help from the samba server administrator. Is this a workplace server?

pier_andreit · November 5, 2019, 11:24am

pla@pla4-TW:~> firewall-cmd --state
not running
pla@pla4-TW:~> firewall-cmd --list-services
FirewallD is not running
pla@pla4-TW:~>

I cannot have any help from the samba server administrator, it’s a server in a workplace network but not a a workplace server and I don’t know the administrator of this server.
but it seems to me a tumbleweed problem I think, in the same laptop I have a triboot with a leap 15.1 system and there it works fairly, I don’t know if the version is the culprit, as it is the only difference, as shown in the previous smbclient test
in the non working tumbleweed system

pla@pla4-TW:~> smbclient -m smb2 -L 192.168.204.86 -d 3
......
Client started (version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64).

in the leap 15.1 working system

iner@LE6-SABC-hw:~> smbclient -m smb2 -L 192.168.204.86 -d 3              
.....
Client started (version 4.9.5-git.187.71edee57d5alp151.2.6.1-SUSE-oS15.0-x86_64).

and I don’t know if the 4.11.0 version doesn’t treat differently the problem that appeared in both cases

directory_create_or_exist_strict: invalid ownership on directory /var/lib/samba/lock/msg.lock
cmdline_messaging_context: Unable to initialize messaging context.
Unable to initialize messaging context

deano_ferrari · November 5, 2019, 6:30pm

pier_andreit:

I cannot have any help from the samba server administrator, it’s a server in a workplace network but not a a workplace server and I don’t know the administrator of this server.
but it seems to me a tumbleweed problem I think, in the same laptop I have a triboot with a leap 15.1 system and there it works fairly, I don’t know if the version is the culprit, as it is the only difference, as shown in the previous smbclient test
in the non working tumbleweed system
pla@pla4-TW:~> smbclient -m smb2 -L 192.168.204.86 -d 3
......
Client started (version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64).
in the leap 15.1 working system
iner@LE6-SABC-hw:~> smbclient -m smb2 -L 192.168.204.86 -d 3              
.....
Client started (version 4.9.5-git.187.71edee57d5alp151.2.6.1-SUSE-oS15.0-x86_64).
and I don’t know if the 4.11.0 version doesn’t treat differently the problem that appeared in both cases
directory_create_or_exist_strict: invalid ownership on directory /var/lib/samba/lock/msg.lock
cmdline_messaging_context: Unable to initialize messaging context.
Unable to initialize messaging context

I’m at the limits of my knowledge here, but I do recall this thread
https://www.linuxquestions.org/questions/linux-server-73/cannot-start-samba-4175625224/
describing similar permissions issues, but the system was a samba server in that case (as opposed to your client situation).

You may want to post this issue in a mailing list (or IRC perhaps)…
https://www.samba.org/

pier_andreit · November 7, 2019, 6:42pm

it seems that permission are ok: /var/lib/samba/private/ should be 755 so if I red well rwxr-xr-x

pla4-TW:~ # ls -la /var/lib/samba/private/
total 844
drwxr-xr-x  3 root root   4096 Oct 30 12:07 .
drwxr-xr-x 11 root root   4096 Nov  5 02:46 ..
drwx------  2 root root   4096 Nov  7 18:12 msg.sock
-rw-------  1 root root 421888 Oct 30 12:07 passdb.tdb
-rw-------  1 root root 430080 Oct 30 12:07 secrets.tdb

/var/lib/samba/private/msg.sock should be 700 so if I red well rwx------

pla4-TW:~ # ls -la /var/lib/samba/private/msg.sock
total 8
drwx------ 2 root root 4096 Nov  7 18:19 .
drwxr-xr-x 3 root root 4096 Oct 30 12:07 ..
srwxrwxrwx 1 root root    0 Nov  4 16:49 1374
srwxrwxrwx 1 root root    0 Nov  4 16:49 1405
srwxrwxrwx 1 root root    0 Nov  4 16:49 1406
srwxrwxrwx 1 root root    0 Nov  4 16:49 1431

/var/lib/samba/lock/msg.lock should be 755 so if I red well rwxr-xr-x

pla4-TW:~ # ls -la /var/lib/samba/lock/msg.lock
total 32
drwxr-xr-x 2 root root 4096 Nov  7 18:21 .
drwxr-xr-x 3 root root 4096 Oct 30 12:07 ..
-rw-r--r-- 1 root root   21 Nov  4 16:49 1374
-rw-r--r-- 1 root root   21 Nov  4 16:49 1405
-rw-r--r-- 1 root root   20 Nov  4 16:49 1406
-rw-r--r-- 1 root root   21 Nov  4 16:49 1431
-rw-r--r-- 1 root root   20 Nov  7 18:21 4511
-rw-r--r-- 1 root root   20 Nov  7 18:21 4512

and also /var/lib/samba/lock/

pla4-TW:~ # ls -la /var/lib/samba/lock/
total 1872
drwxr-xr-x  3 root root   4096 Oct 30 12:07 .
drwxr-xr-x 11 root root   4096 Nov  5 02:46 ..
-rw-r--r--  1 root root 441608 Nov  4 16:49 brlock.tdb
-rw-r--r--  1 root root 454656 Nov  5 02:46 gencache.tdb
-rw-r--r--  1 root root 441580 Aug 20 20:10 gencache_notrans.tdb
-rw-r--r--  1 root root   8888 Nov  4 16:49 leases.tdb
-rw-r--r--  1 root root 441608 Nov  4 16:49 locking.tdb
drwxr-xr-x  2 root root   4096 Nov  7 18:27 msg.lock
-rw-------  1 root root    696 Oct 30 12:07 mutex.tdb
-rw-r-----  1 root root  12288 Nov  4 16:49 names.tdb
-rw-r--r--  1 root root  20480 Nov  7 18:19 printer_list.tdb
-rw-------  1 root root   8888 Nov  4 16:49 smbXsrv_client_global.tdb
-rw-------  1 root root   8888 Nov  4 16:49 smbXsrv_open_global.tdb
-rw-------  1 root root   8888 Nov  4 16:49 smbXsrv_session_global.tdb
-rw-------  1 root root   8888 Nov  4 16:49 smbXsrv_tcon_global.tdb
-rw-------  1 root root  24576 Nov  4 16:49 smbXsrv_version_global.tdb

manythanks, I’ll try