I'm wondering how smb4k queries the network for available servers and workgroups.
smbtree, smbclient -L localhost, dolphin samba shares, and dolphin network (zeroconf?) all see all the machines on my network and I can access them.
smb4k does not see my home workgroup.
My laptop is on its own workgroup, but that has never been an issue until recently. I'm not sure if updates to smb4k or to samba caused it, but either way - I would assume smb4k should see what every other tool manages to.
Just noticed that nmblookup -M - does not return the other server's IP address as an available browse master. Perhaps that's it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nope. That's not it. I disabled my wifi interface, because it was using that, and set interfaces to only use eno1 and set bind interfaces to yes.
nmblookup -M - is now returning both of the correct browse masters on my network, as are all other methods, except for smb4k, which does not show the home workgroup "workgroup".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Smb4K 3.0.1 uses libsmbclient, not Samba's utility programs anymore. Have you adjusted your smb.conf file according to note given in the announcement of Smb4K 3.0.0? Does the Samba KIO slave (e.g. in Dolphin) work?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't, because it worked with the 2.9 smb4k series w/o doing it and I've been on samba newer than 4.7 for a long time, and Dolphin was happy then also. Running Arch.
I guess I'm not sure how I got away with until now?
I wonder if server side changes were the cause? The workgroup master that's not showing up has been updated to Arch as well.
Mostly, I just wanted to understand why smb4k would differ from what everything else is doing, and/or why it couldn't do things the same way, which works?
Last edit: Jason Straight 2019-07-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, the change happened before releasing version 2.9.70. If you could work with the beta versions, you should also be able to work with the stable ones. So, I am a bit confused.
Does the SMB KIO slave also does not work no? If that is the case, the "problem" most likely is Samba-related. Adjusting the smb.conf file should then do the trick. If the SMB Kio slave in Dolphin works as expected, please tell me.
Changes on the server side never were an issue for browsing and mounting under Linux. So, I think that can be canceled out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah. It's strange. The kio works with or without NT1 client max.
I'm at work now, where it also used to work, but doesn't any more, and nothing has changed on the network there, like at home, where the SMB master is now Arch.
Here, at work, it's still ubuntu 18.04.
Does smb4k still obey the interfaces parameter from smb.conf?
Something I've had problems with in the past with it is when I have multiple network interfaces, like wired, wifi, and several virtual ones for vm's and containers.
I set interfaces in smb.conf to only use eno1 (wired), but that had no effect with smb4k, although it did help nmblookup -M - to use the right device to find masters.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Smb4K should obey the interfaces parameter, as long as libsmbclient does.
What is strange is, that Dolphin works but Smb4K does not. That puzzels me. And I do not have a clou at the moment, why that is. Maybe I have to look at the code ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At home, I have a Manjaro browse master with Windows 10 and Linux and everything shows up.
At work, I have an ubuntu server/master with a mixed network with Win10/7, My Manjaro laptop, and several Toshiba MFP's that I assume are running some version of SAMBA/Linux. Nothing shows up in SMB4k at work, but dolphin works fine.
I'm at a loss as to what to do to get more useful information as to why it's failing at work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I recently stumbled across this phenomenon as well. It occurred when no IP address could be detected. In the code all entries are neglected that have no IP address. Maybe this is the case here.
I can produce a modified version, so that all detected servers are taken into account. Would you be willing to test it? (Note: It might be that mounting is broken then. At least I experienced this issue.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm wondering how smb4k queries the network for available servers and workgroups.
smbtree, smbclient -L localhost, dolphin samba shares, and dolphin network (zeroconf?) all see all the machines on my network and I can access them.
smb4k does not see my home workgroup.
My laptop is on its own workgroup, but that has never been an issue until recently. I'm not sure if updates to smb4k or to samba caused it, but either way - I would assume smb4k should see what every other tool manages to.
Just noticed that nmblookup -M - does not return the other server's IP address as an available browse master. Perhaps that's it?
Nope. That's not it. I disabled my wifi interface, because it was using that, and set interfaces to only use eno1 and set bind interfaces to yes.
nmblookup -M - is now returning both of the correct browse masters on my network, as are all other methods, except for smb4k, which does not show the home workgroup "workgroup".
Can you please tell me which version of Smb4K you are using?
3.0.1
Smb4K 3.0.1 uses libsmbclient, not Samba's utility programs anymore. Have you adjusted your smb.conf file according to note given in the announcement of Smb4K 3.0.0? Does the Samba KIO slave (e.g. in Dolphin) work?
I didn't, because it worked with the 2.9 smb4k series w/o doing it and I've been on samba newer than 4.7 for a long time, and Dolphin was happy then also. Running Arch.
I guess I'm not sure how I got away with until now?
I wonder if server side changes were the cause? The workgroup master that's not showing up has been updated to Arch as well.
Mostly, I just wanted to understand why smb4k would differ from what everything else is doing, and/or why it couldn't do things the same way, which works?
Last edit: Jason Straight 2019-07-29
Oh, so the change to libsmbclient was after 2.9? That makes sense then.
Turns out that wasn't it anyway. I added max client of NT1 to the laptop and it still cannot see the workgroup/server.
samba utils and dolphin smb: and zeroconf: both still find the other machines on the network and in the workgroup.
Thank you for trying. That's strange, though.
No, the change happened before releasing version 2.9.70. If you could work with the beta versions, you should also be able to work with the stable ones. So, I am a bit confused.
Does the SMB KIO slave also does not work no? If that is the case, the "problem" most likely is Samba-related. Adjusting the smb.conf file should then do the trick. If the SMB Kio slave in Dolphin works as expected, please tell me.
Changes on the server side never were an issue for browsing and mounting under Linux. So, I think that can be canceled out.
Yeah. It's strange. The kio works with or without NT1 client max.
I'm at work now, where it also used to work, but doesn't any more, and nothing has changed on the network there, like at home, where the SMB master is now Arch.
Here, at work, it's still ubuntu 18.04.
Does smb4k still obey the interfaces parameter from smb.conf?
Something I've had problems with in the past with it is when I have multiple network interfaces, like wired, wifi, and several virtual ones for vm's and containers.
I set interfaces in smb.conf to only use eno1 (wired), but that had no effect with smb4k, although it did help nmblookup -M - to use the right device to find masters.
Smb4K should obey the interfaces parameter, as long as libsmbclient does.
What is strange is, that Dolphin works but Smb4K does not. That puzzels me. And I do not have a clou at the moment, why that is. Maybe I have to look at the code ...
Sometimes I really hate samba.
This is strange. At work, nmblookup -M - only shows me one master, unless I specify the broadcast address.
[V junfan]# nmblookup -M -
192.168.0.99 MSBROWSE<01>
[V junfan]# nmblookup -B 192.168.0.255 -M -
querying MSBROWSE on 192.168.0.255
192.168.0.216 MSBROWSE<01>
192.168.0.99 MSBROWSE<01>
Still having fun with this at work.
At home, I have a Manjaro browse master with Windows 10 and Linux and everything shows up.
At work, I have an ubuntu server/master with a mixed network with Win10/7, My Manjaro laptop, and several Toshiba MFP's that I assume are running some version of SAMBA/Linux. Nothing shows up in SMB4k at work, but dolphin works fine.
I'm at a loss as to what to do to get more useful information as to why it's failing at work.
I recently stumbled across this phenomenon as well. It occurred when no IP address could be detected. In the code all entries are neglected that have no IP address. Maybe this is the case here.
I can produce a modified version, so that all detected servers are taken into account. Would you be willing to test it? (Note: It might be that mounting is broken then. At least I experienced this issue.)