Bug 30788

1-Message displayed after on share connection attempt is :

File or folder smb://user@host doesn't exist.

2- coming back to previous version restore normal behaviour :

lib64kdc-samba4_2-4.14.12-1.mga8.x86_64
samba-4.14.12-1.mga8.x86_64
samba-client-4.14.12-1.mga8.x86_64
lib64smbclient0-4.14.12-1.mga8.x86_64
lib64samba1-4.14.12-1.mga8.x86_64
lib64wbclient0-4.14.12-1.mga8.x86_64
samba-common-4.14.12-1.mga8.x86_64
lib64samba-dc0-4.14.12-1.mga8.x86_64

Which DE is used? How do you try to access the share (command line or filemanger....)

If you use Plasma and Dolphin:
System Settings–>Network Settings–>Windows Shares, add ANY text to the user and password fields and restart Dolphin.

https://forum.manjaro.org/t/dolphin-the-file-or-folder-smb-sharename-does-not-exist/114900/9

Comment 2 seems clear enough.
An update should not break a working state - unless perhaps that was in some way unusual (configuration) which worked by chance up to now, but not henceforth.

If further investigation as per sturmvogel gets nowhere, assign eventually to buchan.

Thanks all for your help and advices.

I use Plasma and Dolphin to access my shares and hostnames rather than IP addresses but I tried with IP addresses too without success.

Regarding the turnaround proposed by sturmvogel, I already access my windows shares through a username and password.

It works like that with samba 4.14.12 and not with 4.14.14-1

FYI it seems that SMB network discovery doesn't work but in Windows 10 either.

So to access shares with samba 4.14.12 , I have to name at least the host or user+host.

(In reply to pat dealt from comment #4)
> Thanks all for your help and advices.
> 
> I use Plasma and Dolphin to access my shares and hostnames rather than IP
> addresses but I tried with IP addresses too without success.
> 
> Regarding the turnaround proposed by sturmvogel, I already access my windows
> shares through a username and password.
> 
> It works like that with samba 4.14.12 and not with 4.14.14-1
> 
> FYI it seems that SMB network discovery doesn't work but in Windows 10
> either.
> 
> So to access shares with samba 4.14.12 , I have to name at least the host or
> user+host.

Assigning to our registered samba maintainer.

Assignee: bugsquad => bgmilne
CC: (none) => marja11

I noticed that my samba client using gnome nautilus is unable to connect to smb shares any longer.  Windows machines can.  

Is this the same issue?  If so, I believe it may be related to red hat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2068976. Which states "upgrading GVFS packages to recent version 1.48.1-3 solved the smb mounting issue with Gnome Files (Nautilus)"

Can we follow the same.  My SMB clients are broke at the moment.

CC: (none) => brtians1

Just to complete :

It seems that with samba-4.14.14-1.mga8.x86_64 the access to Windows hosts is working from Mageai 8 through a command line in a konsole (smbclient //host/share + password).

So this samba update bug has something to do with plasma dolphin and may be also gnome nautilus.

A connection attempt shows the following error :

File or folder smb://user@host/share doesn't exist.

Is possible that need to make a small change on the smb.conf file
If you have the line 

map to guest = bad user

you need to change to 

map to guest = bad password

https://wiki.archlinux.org/title/samba#Windows_clients_keep_asking_for_password_even_if_Samba_shares_are_created_with_guest_permissions

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30984

Answer to comment 8 from katnatek

On my configuration map to guest is not set, so the default value is "Never".

Nevermind, I tried with "bad password" value.
The result is the same : connection is authorised with smbclient but not with dolphin.