Hai All,
I installed samba server on Debian Bullseye in my home PC Server. Only in fedora 36 workstation with Files file manager(There is not problem in fedora 35 workstation). I can’t access samba share, but I can acess it from terminal. See my SS below:
Unable to open location.
Failed to associate windows share system.
Invalid argument
How I solve this problem.
Thank You in Advance.
Can you access it by typing smb://192.168.1.4 in connect to server.
Yes of course. See my SS below, the popup error message appears when I doubled click in example DATA02.
Thank You.
I haven’t tried using samba on F36 but like you I do have it set up on F35 and have no issues.Unless something in the firewall or selinux has changed I’m sorry I can’t help.
Yes you’re right I don’t have this issue in fedora 35. I don’t know because I don’t change anything in this fedora 36 pre-release, samba client is default install and gvfs-smb is already installed:
sudo dnf install gvfs-smb
Last metadata expiration check: 0:35:20 ago on Sab 26 Mar 2022 04:40:37 .
Paket gvfs-smb-1.50.0-2.fc36.x86_64 telah terpasang.
Dependensi terselesaikan.
Tidak ada yang dilakukan.
Selesai!
May be because all services are not optimized for f36 i haven’t installed 36 but i will try on vm once beta get released.
I just installed F36 in virtualbox and set up samba the same way as F35 and I can see the folders on the other networks as Afiadi posted but have the same error.In F35 there’s no issues.
Just to add I followed the info on Files (Nautilus) 42.0 fails to connect to network drive (#611) · Issues · GNOME / gvfs and downgraded libsmbclient and file sharing is now working in Fedora36.I’m sure the fix will be in the repos soon.
The same error, i read this post today.
I have reported to bugzilla 2068867.
it have reported blockquote first, my bug report is duplicated.
Just to add I followed the info on Files (Nautilus) 42.0 fails to connect to network drive (#611) · Issues · GNOME / gvfs and downgraded libsmbclient and file sharing is now working in Fedora36.I’m sure the fix will be in the repos soon.
I think is fixed now, I don’t need to downgrade libsmbclient, nautilus can access file server samba normally with the lastest version of samba.
how do you install the lastest version from the samba repo in fedora 36. I can’t seems to it install.
Please help. Thanks.
in a terminal window the command dnf upgrade \*smb* will verify the latest is installed since smb (samba) is normally installed by default in fedora.
Jeff,
Thanks for your prompt respond.
upgrade does not find any new version, instead it works with downgrade.
I am sure this will be solve when it is officially release.
Thanks.
Maybe I must change the solution,to make you understand. I checked the solution in this thread with sudo dnf downgrade libsmbclient is before dev fedora fixed this samba share update in fedora 36 beta. Then after I do that, couple days later I do like usual sudo dnf update. If i do dnf update so automatically all samba package which i downgrade before is updating too. I realize this, then I try to open file manager and voila access samba server with file manager in fedora 36 beta is working. so I update in this thread and doesn’t change checked solution.
Finally you don’t need to downgrade samba package in fedora 36 beta to access samba server because is already fixed. just type sudo dnf update. Oke I change the solution for this thread.
HTH.
I have the updated version but still unable to access the samba, may be like you mentioned that the solution need to downgrade first then it will work with the updated version.
Anyway, let me try to update now and feedback if it is working.
Thanks.
I went ahead and upgraded from F35 to F36 and samba is working.I don’t think it was as much a samba issue but gvfs.Either way it seems to be working now in F36.
Tthat is great news. At least i know upgrading to F36 will not have problem
Thanks.
