Initial bug: https://gitlab.gnome.org/GNOME/gvfs/-/issues/567 Code to reproduces: smbclient //mydomain.local/public/ -U danylo.korostil smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it Enter WORKGROUP\danylo.korostil's password: Try "help" to get a list of possible commands. smb: \> ls . D 0 Thu May 28 17:29:24 2020 .. D 0 Thu May 28 17:29:24 2020 autotests Dr 0 Thu May 28 17:29:24 2020 Projects Dr 0 Wed Mar 11 09:30:58 2020 Users Dr 0 Thu Nov 14 13:13:56 2019 15728127 blocks of size 4096. 4494102 blocks available smb: \> cd Users do_connect: Connection to pro-file-01 failed (Error NT_STATUS_NOT_FOUND) Unable to follow dfs referral [\pro-file-01\pro-backup] cd \Users\: NT_STATUS_NOT_FOUND
What happens if you do: dir Users instead of: cd Users ?
smb: \> dir Users do_connect: Connection to pro-file-01 failed (Error NT_STATUS_NOT_FOUND) Unable to follow dfs referral [\pro-file-01\pro-backup] do_list: [\Users] NT_STATUS_NOT_FOUND 15728127 blocks of size 4096. 4528995 blocks available
Any further logs or actions required to make it clear?
"mydomain.local" looks like this is a DNS zone name, is this your AD DC realm and you are connecting to that one? If this is an AD DC, can you please try the same of a member file server? Your smb.conf would be good to see. Also a "ls -l" of the filesystem folder of the "public" share. You reported this against 4.14.4, did you see the same with previous versions also? Is the server actually samba 4.14.4 or is the client side samba 4.14.4 or both?
Yeah, it seems like the AD DC realm. Sorry, I didn't get this "please try the same of a member file server". What exactly should I run? I don't have any smb.conf. I used nautilus/gio to connect to this resource. Please see for more information here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/567 samba --version Version 4.14.4 I'm using gio (not sure whether they use server/client/both) and haven't tried the other version.
(In reply to Danylo Korotil from comment #5) I think what Bjorn is trying to say is that you seem to be trying to connect to a dns domain rather than to a specific computer. Is 'mydomain,local' a dns domain name ? If it is a domain name, does 'smbclient //server.mydomain.local/public/ -U danylo.korostil' work ? Where 'server' is the hostname for the computer that holds the 'public' share.
Thanks, Rowland! Unfortunately, I know too little about this server configuration, honestly. It's a kind of file share or something (I'm not really into it). However, it works fine from my Windows machine and never asks for the server name or whatever. Can I find out the server name using the Windows machine?
(In reply to Danylo Korotil from comment #7) I think you need to find out more about your setup, especially the hostname of the server. To connect to a share with smbclient, you need to use: //server/service Where 'server' can be the NETBios name, or short hostname, or the FQDN, or the ipaddress of the computer that holds the share. 'service' is another name for the share name. Your 'mydomain.local' looks suspiciously like a dns domain and if it is, it would (from my experience) only work with the sysvol & netlogon shares on a Samba AD DC. If you type 'hostname -d' into the machine where you are running smbclient, does it return 'mydomain.local' ?
(In reply to Danylo Korotil from comment #7) Okay, who thought using 'mydomain' as a HOST name was a good idea ? Yes 'mydomain.local' is a mdns name and there isn't really a problem, because the command given is trying to follow a DFS link, so this: smbclient //mydomain.local/public/ -U danylo.korostil should be this: smbclient //mydomain.local/public/ -U WORKGROUP_OF_THE COMPUTER_HOLDING__DFS_SHARE\\danylo.korostil This isn't a Samba problem, it is a misconfiguration.
But why does it work without providing server on Windows machines? Is there some technical limitation samba can't overcome? I mean why the experience for regular users should be different? Get me right, it's not something I'm complaining, but I want to get the idea behind "why it doesn't fail on Windows machines out of the box if it looks so wrong". Thanks in advance!
(In reply to Danylo Korotil from comment #10) No, I (and Bjorn) was looking at it wrong, 'mydomain.local' is the MDNS name for your computer. The 'mydomain' part is your computers short hostname and the '.local' part is coming from Avahi (or Bonjour if you are using a Mac), so your smbclient command works up to a point, the point being the DFS link. DFS links work by connecting to a share on another machine and your user needs to have permission to connect to the ultimate share, you need to add the workgroup of the computer that holds your DFS share to your smbclient command. I tried every thing I could, but I couldn't make the command fail, I then realised that I was also dealing with a DFS link (I really read what you posted, both here and on your link). If the correct command is run, it works, you are not using the correct command so it doesn't. If your computer wasn't using 'mydomain' as its short hostname, this would probably have been realised earlier. smbclient is working as expected, if it doesn't work from the gnome app, then there is possibly something wrong with that (or it could be misconfigured).
Closing this, it has been over 14 days since last reply from Danylo and it works for me.