I am running openSUSE Leap on my macines and when I update from Samba 4.2.4-12.1 to 4.2.4-15.1 I find that SMB4K (1.2.1-36.22) no longer works properly. The program opens and I can scan the network which shows the workgroup name just fine but when I try to scan the workgroup I find the name simply disappears from view although a scan network shows it again. Also I can use the search function and find my Linus shares OK although the Windows PC shares do not show up on a search. Now I know someting has changed in this update to Samba but Samba itself seems to be working and I can use the smb:// protocol in say Dolphin and it works. The Windows PC can see and use the Linux shares with no issues at all. Running SMB4K from the command line with no fork shows the following messages
smb4k --nofork
Object::connect: No such signal org::freedesktop::UPower::Device::Changed()
Object::connect: No such signal org::freedesktop::UPower::Device::Changed()
Object::connect: No such signal org::freedesktop::UPower::Device::Changed()
smb4k(5782)/kdeui (KIconLoader) KIconLoaderPrivate::normalizeIconMetadata: Neither size nor group specified!
Smb4KSolidInterface Removed device: "/org/freedesktop/UPower/devices/mouse_0003o046Do1017x000A"
Solid::Backends::UDev::input_str_to_bitmask can't handle some bits ("3007f", "0", "0", "0", "0", "483ffff", "17aff32d", "bf544446", "0", "0", "1", "130c13", "b17c000", "267bfa", "d941dfed", "9e1680", "4400", "0", "10000002")
Smb4KSolidInterface Added device: "/org/freedesktop/UPower/devices/mouse_0003o046Do1017x0010"
So is there something I should do to try to find out why this is happening in SMB4K?
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As far as I remember, this should only happen (disappearance of the workgroup emtry) if the scan for workgroup members fails, i. e. the master browser returns an empty list. Could you please run the following command from the command line:
$ net rap server domain -S <your_master_browser>
What does the output say?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have found this problem to be in just about every distro released in the last two months. I placed links to shares on my desktop to get around, but I don't like it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This weekend I upgraded my laptop from Kubuntu 15.10 to 16.04 and was also affected by this issue. Searching the web revealed that there are problem reports all over the place... Maybe we have to wait for the next Samba release until this issue is resolved.
Last edit: Alexander Reinholdt 2016-04-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Interestingly I have dual booted now openSUSE Tumbleweed which has Samba 4.4 and that has the issue, so looks like everything from 4.2.4 up can be affected. The command on 4.4 fails but with a different message than that on 4.2.4 but the result is the same. I cam still able to use SMB4K as my bookmarks will still mounth the remote disks I need.
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is a bug report on bugzilla.samba.org where the problem we encountered is discussed. The reporter also provided a combination of settings (see comment 11) that have to be put into the [global] section of the smb.conf file to make the net command work again:
client max protocol = SMB3
client ipc max protocol = NT1
I tested this and it works.
However, I consider this only as temporarily needed, since there are already patches available (see comment 14) that hopefully will be rolled out soon.
Last edit: Alexander Reinholdt 2016-04-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, i don't know if im in the wrong place or if this should be on stackexhange.
I've been using Smb4k for a while to make mounting file shares as easy on my kUbuntu machines as it is on my window boxes, android devices, and osx devices.
As of today I realized that neither of my two kUbuntu 14.04LTS machines can see any shares under the workgroup. If I put in the ip address of one share under
Configure > Network > 'Scan these broadcast areas",
it will show the server name for that computer but forces me to login with one of the shares user/passwords just to see a list of avalible shares under that server.
Before, all I did was launch Smb4K and click on the network neighborhood tab and I could see all servers from every computer on the network that is sharing. I could also see all folders shared under each server by clicking on the server and it wouldn't prompt for a password until I tried to access an actual directory.
Can anyone provide any feeback to help me figure out why Smb4k on both my kUbuntu machines are not acting normally or how to troubleshoot?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Most likely you are experiencing the same issue as many others after they updated Samba with the security fixes released on April, 12th. Please try the workaround given above. Does Smb4K work again as execpted?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The work around worked for me in Leap and also other distros. In Tumbleweed, however, another problem presents itself. I can mount shares, but when I try to access them from smb4k I get a Could not find any application or handler for <share>.
Last edit: Thomas Mahoney 2016-05-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can't say I noted any issues until last week.
The bug fix hasn't fixed my system! kubuntu 16.04
Dolphin and Knetattach still work fine.
Purged and installed smb4k_1.1.2-1
Getting can't mkdir permission denied on
/var/run/samba/msg.lock
Fixed that issue by changing permissions to 775 on the samba directorywhich then brings up the error
signing_good: BAD SIG: seq 1: This error is mentioned in numerious bugs dating back to 2010.
Also I noted the .kde/shares/apps/smb4k/custom.xml file was not being created and the custom section on the app was greyed out until I copied an old copy over.
Pulled enough hair out on this one for now. Pain in the A as I have to create dozens of manual links.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is very strange. I also use Kubuntu and do not have any of those issues you are reporting. What happened before the permissions of the msg.lock directory changed? Just the reinstall of Smb4K?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
just build 1.2.2 stable and this appears to be not fixed: no lookup possible using the "net" method, changing the method to "nmblookup" does not help either. "net rap server domain -S MYMASTERBROWSER" is still empty after the password query.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This same issue of the workgroup name disappearing when it is scanned is happening again using Samba 4.6.7 on openSUSE Leap 42.3 and Tumbleweed also with 4.6.7. The net rap command suggested here returns a empty list of servers despite there being 2 link and one windows systems on the lan all of which are accessible from each other. This seems to have started following a patch to Samba as on both systems the release is updated by a git patch. When I downgraded Samba to 4.6.5 the workgroup does not disappear but the messaging context error happens. Looks like a patch to 4.6.7 seems to cause this. Does not matter whether I use the additions to smaba.conf of SMB3 and NT1 or not with 4.6.7 the workgroup disappears on scanning.
Stuart
Last edit: Stuart 2017-09-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm comparing the behavior of smb4k on a Debian system using Samba 4.1.17 (SYSTEM1) vs. smb4k on a Debian system using Samba 4.7.4 (SYSTEM2).
Both Debian Systems belong to workgroup GROUP1.
SYSTEM3 is Windows Server 2003 belonging to GROUP2 and is master browswer of GROUP2 most of the time.
a) on both systems on startup of smb4k the two workgroups (GROUP1 and GROUP2) appear in the Network-Browser-Tab
b) on SYSTEM1: clicking on the two workgroup entries opens the tree and shows the servers belonging to the corresponding group
c) on SYSTEM2: clicking on GROUP1 makes disappearing the entry, clicking on GROUP2 makes popping up an error message saying:
could not connect to server SYSTEM3 (SYSTEM3 is the master browser of GROUP2)
Connection failed:
NT_STATUS_INVALID_PARAMETER
I suppose this is an error message of a net command.
So I checked the net command which is used by smb4k to look up the servers belonging to a workgroup,
something like net rap server domain -U % -S SYSTEM2
(when SYSTEM2 is the current the master browser)
It seems there are four cases:
1) SYSTEM1 calls SYSTEM2 (i.e. samba 4.1.17 calls debian system)
2) SYSTEM1 calls SYSTEM3 (i.e. samba 4.1.17 calls Windows Server in foreign workgroup)
3) SYSTEM2 calls SYSTEM2 (i.e. samba 4.7.4 calls debian system (calling itself because of being master)
4) SYSTEM2 calls SYSTEM3 (i.e. samba 4.7.4 calls Windows Server in foreign workgroup)
Results on command line:
1) everything ok, servers of GROUP1 are listed
2) everything ok, servers of GROUP2 are listed
3) empty server list !
4) connection failed: NT_STATUS_INVALID_PARAMETER
Observations on wireshark
1) package SMB Session Setup AndX Request, User: anonymous
which contains SMB Header Flags2: 0x843
one of the meaning of 0x843 is: security signatures neither required nor supported
2) same as 1)
3) package SMB Session Setup AndX Request, NTLMSSP_NEGOTIATE
which contains SMB Header Flags2: 0x857
one of the meaning of 0x857 is: security signatures ARE required and supported
package SMB Session Setup AndX Request, NTLMSSP_AUTH, User: \
4) same as 3)
Summary:
there were changes in net command:
a) use of -U % doesn't result in "User: anonymous" any more but in "User: \"
b) Flags2 changed from 0x843 to 0x857 which means security signatures required
Consequences:
a) "User: \" leads to Invalid_Parameter on some master browser systems so smb4k is kind of confused
b) the required use of security signatures probably needs corresponding settings on all potential master browswer servers,
perhaps something like "return browse list" has to be permitted and corresponding authentication data has to be transfered...?
Or is it possible with commandline options or smb.conf settings to come back to Flags2 = 0x843 ?
Hope this helps somebody on fixing smb4k and / or samba.
Last edit: J.M. 2018-02-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have a fully updated Opensuse Leap 15.0 , with smb4k 2.1.1 from wolfi323 repo. Me neither i can browse the network neighborhood. I get the error at the attached screenshot.
I have also tried smb4k 2.1.70 from repo https://build.opensuse.org/package/show/KDE%3AUnstable%3AExtra/smb4k but the issue is still present.
Unfortunately smb4k is barely usable without being able to browse the network neighborhood.
Alexander do you plan to publish a fix?
EDIT
I disabled firewalld and apparmor. The screenshot error dissapeared, the one workgroup that exists on my network appears but when i try to browse it i do not get any results for the available computers with shares.
I just tried OpenSUSE Leap. Unfortunately, Samba 4.7.x is also affected by the problem I wrote about in the handbook (see here). The command
$ net rap server domain -S [server]
fails due to a regession that was introduced during development. More information can be acquired from this conversation on samba-technical.
Since this is a problem in Samba, I cannot fix it in Smb4K. There are actually three routes to make Smb4K work probperly again:
Open a bug report either with your distribution or better with Samba (Samba's issue tracker is here) asking them to fix Samba (a patch is provided in the above mentioned conversation).
Patch Samba yourself, compile and install it. That's the way I do it at the moment. Use the patch provided in the conversation for this.
Rewrite the sanner code of Smb4K to not use the Samba programs anymore but use libsmbclient directly. That's a way I'm thinking about right now. But that would involve a major rewrite which would take some time.
Last edit: Alexander Reinholdt 2018-08-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running openSUSE Leap on my macines and when I update from Samba 4.2.4-12.1 to 4.2.4-15.1 I find that SMB4K (1.2.1-36.22) no longer works properly. The program opens and I can scan the network which shows the workgroup name just fine but when I try to scan the workgroup I find the name simply disappears from view although a scan network shows it again. Also I can use the search function and find my Linus shares OK although the Windows PC shares do not show up on a search. Now I know someting has changed in this update to Samba but Samba itself seems to be working and I can use the smb:// protocol in say Dolphin and it works. The Windows PC can see and use the Linux shares with no issues at all. Running SMB4K from the command line with no fork shows the following messages
smb4k --nofork Object::connect: No such signal org::freedesktop::UPower::Device::Changed() Object::connect: No such signal org::freedesktop::UPower::Device::Changed() Object::connect: No such signal org::freedesktop::UPower::Device::Changed() smb4k(5782)/kdeui (KIconLoader) KIconLoaderPrivate::normalizeIconMetadata: Neither size nor group specified! Smb4KSolidInterface Removed device: "/org/freedesktop/UPower/devices/mouse_0003o046Do1017x000A" Solid::Backends::UDev::input_str_to_bitmask can't handle some bits ("3007f", "0", "0", "0", "0", "483ffff", "17aff32d", "bf544446", "0", "0", "1", "130c13", "b17c000", "267bfa", "d941dfed", "9e1680", "4400", "0", "10000002") Smb4KSolidInterface Added device: "/org/freedesktop/UPower/devices/mouse_0003o046Do1017x0010"So is there something I should do to try to find out why this is happening in SMB4K?
Stuart
As far as I remember, this should only happen (disappearance of the workgroup emtry) if the scan for workgroup members fails, i. e. the master browser returns an empty list. Could you please run the following command from the command line:
What does the output say?
Alexander that command does indeed return and empty list where the previous verion returns a populated list.
So I guess this is a Samba problem not one of SMB4K making. I'll need to get that reported in openSUSE I guess.
Stuart
I have found this problem to be in just about every distro released in the last two months. I placed links to shares on my desktop to get around, but I don't like it.
This weekend I upgraded my laptop from Kubuntu 15.10 to 16.04 and was also affected by this issue. Searching the web revealed that there are problem reports all over the place... Maybe we have to wait for the next Samba release until this issue is resolved.
Last edit: Alexander Reinholdt 2016-04-25
Interestingly I have dual booted now openSUSE Tumbleweed which has Samba 4.4 and that has the issue, so looks like everything from 4.2.4 up can be affected. The command on 4.4 fails but with a different message than that on 4.2.4 but the result is the same. I cam still able to use SMB4K as my bookmarks will still mounth the remote disks I need.
Stuart
There is a bug report on bugzilla.samba.org where the problem we encountered is discussed. The reporter also provided a combination of settings (see comment 11) that have to be put into the [global] section of the smb.conf file to make the net command work again:
I tested this and it works.
However, I consider this only as temporarily needed, since there are already patches available (see comment 14) that hopefully will be rolled out soon.
Last edit: Alexander Reinholdt 2016-04-30
Hello, i don't know if im in the wrong place or if this should be on stackexhange.
I've been using Smb4k for a while to make mounting file shares as easy on my kUbuntu machines as it is on my window boxes, android devices, and osx devices.
As of today I realized that neither of my two kUbuntu 14.04LTS machines can see any shares under the workgroup. If I put in the ip address of one share under
Configure > Network > 'Scan these broadcast areas",
it will show the server name for that computer but forces me to login with one of the shares user/passwords just to see a list of avalible shares under that server.
Before, all I did was launch Smb4K and click on the network neighborhood tab and I could see all servers from every computer on the network that is sharing. I could also see all folders shared under each server by clicking on the server and it wouldn't prompt for a password until I tried to access an actual directory.
Can anyone provide any feeback to help me figure out why Smb4k on both my kUbuntu machines are not acting normally or how to troubleshoot?
Most likely you are experiencing the same issue as many others after they updated Samba with the security fixes released on April, 12th. Please try the workaround given above. Does Smb4K work again as execpted?
The work around worked for me in Leap and also other distros. In Tumbleweed, however, another problem presents itself. I can mount shares, but when I try to access them from smb4k I get a Could not find any application or handler for <share>.
Last edit: Thomas Mahoney 2016-05-29
SMB4K works again for me with those two lines added to the global section of smb.conf, however it does break Dolphin accessing Samba shares.
Stuart
Can't say I noted any issues until last week.
The bug fix hasn't fixed my system! kubuntu 16.04
Dolphin and Knetattach still work fine.
Purged and installed smb4k_1.1.2-1
Getting can't mkdir permission denied on
/var/run/samba/msg.lock
Fixed that issue by changing permissions to 775 on the samba directorywhich then brings up the error
signing_good: BAD SIG: seq 1: This error is mentioned in numerious bugs dating back to 2010.
Also I noted the .kde/shares/apps/smb4k/custom.xml file was not being created and the custom section on the app was greyed out until I copied an old copy over.
Pulled enough hair out on this one for now. Pain in the A as I have to create dozens of manual links.
This is very strange. I also use Kubuntu and do not have any of those issues you are reporting. What happened before the permissions of the msg.lock directory changed? Just the reinstall of Smb4K?
Does anyone know when/if this issue will be properly resolved?
just build 1.2.2 stable and this appears to be not fixed: no lookup possible using the "net" method, changing the method to "nmblookup" does not help either. "net rap server domain -S MYMASTERBROWSER" is still empty after the password query.
This same issue of the workgroup name disappearing when it is scanned is happening again using Samba 4.6.7 on openSUSE Leap 42.3 and Tumbleweed also with 4.6.7. The net rap command suggested here returns a empty list of servers despite there being 2 link and one windows systems on the lan all of which are accessible from each other. This seems to have started following a patch to Samba as on both systems the release is updated by a git patch. When I downgraded Samba to 4.6.5 the workgroup does not disappear but the messaging context error happens. Looks like a patch to 4.6.7 seems to cause this. Does not matter whether I use the additions to smaba.conf of SMB3 and NT1 or not with 4.6.7 the workgroup disappears on scanning.
Stuart
Last edit: Stuart 2017-09-04
I'm comparing the behavior of smb4k on a Debian system using Samba 4.1.17 (SYSTEM1) vs. smb4k on a Debian system using Samba 4.7.4 (SYSTEM2).
Both Debian Systems belong to workgroup GROUP1.
SYSTEM3 is Windows Server 2003 belonging to GROUP2 and is master browswer of GROUP2 most of the time.
a) on both systems on startup of smb4k the two workgroups (GROUP1 and GROUP2) appear in the Network-Browser-Tab
b) on SYSTEM1: clicking on the two workgroup entries opens the tree and shows the servers belonging to the corresponding group
c) on SYSTEM2: clicking on GROUP1 makes disappearing the entry, clicking on GROUP2 makes popping up an error message saying:
could not connect to server SYSTEM3 (SYSTEM3 is the master browser of GROUP2)
Connection failed:
NT_STATUS_INVALID_PARAMETER
I suppose this is an error message of a net command.
So I checked the net command which is used by smb4k to look up the servers belonging to a workgroup,
something like net rap server domain -U % -S SYSTEM2
(when SYSTEM2 is the current the master browser)
It seems there are four cases:
1) SYSTEM1 calls SYSTEM2 (i.e. samba 4.1.17 calls debian system)
2) SYSTEM1 calls SYSTEM3 (i.e. samba 4.1.17 calls Windows Server in foreign workgroup)
3) SYSTEM2 calls SYSTEM2 (i.e. samba 4.7.4 calls debian system (calling itself because of being master)
4) SYSTEM2 calls SYSTEM3 (i.e. samba 4.7.4 calls Windows Server in foreign workgroup)
Results on command line:
1) everything ok, servers of GROUP1 are listed
2) everything ok, servers of GROUP2 are listed
3) empty server list !
4) connection failed: NT_STATUS_INVALID_PARAMETER
Observations on wireshark
1) package SMB Session Setup AndX Request, User: anonymous
which contains SMB Header Flags2: 0x843
one of the meaning of 0x843 is: security signatures neither required nor supported
2) same as 1)
3) package SMB Session Setup AndX Request, NTLMSSP_NEGOTIATE
which contains SMB Header Flags2: 0x857
one of the meaning of 0x857 is: security signatures ARE required and supported
package SMB Session Setup AndX Request, NTLMSSP_AUTH, User: \
4) same as 3)
Summary:
there were changes in net command:
a) use of -U % doesn't result in "User: anonymous" any more but in "User: \"
b) Flags2 changed from 0x843 to 0x857 which means security signatures required
Consequences:
a) "User: \" leads to Invalid_Parameter on some master browser systems so smb4k is kind of confused
b) the required use of security signatures probably needs corresponding settings on all potential master browswer servers,
perhaps something like "return browse list" has to be permitted and corresponding authentication data has to be transfered...?
Or is it possible with commandline options or smb.conf settings to come back to Flags2 = 0x843 ?
Hope this helps somebody on fixing smb4k and / or samba.
Last edit: J.M. 2018-02-07
Hello,
I have a fully updated Opensuse Leap 15.0 , with smb4k 2.1.1 from wolfi323 repo. Me neither i can browse the network neighborhood. I get the error at the attached screenshot.
I have also tried smb4k 2.1.70 from repo https://build.opensuse.org/package/show/KDE%3AUnstable%3AExtra/smb4k but the issue is still present.
Unfortunately smb4k is barely usable without being able to browse the network neighborhood.
Alexander do you plan to publish a fix?
EDIT
I disabled firewalld and apparmor. The screenshot error dissapeared, the one workgroup that exists on my network appears but when i try to browse it i do not get any results for the available computers with shares.
Last edit: Dimitris 2018-08-16
I just tried OpenSUSE Leap. Unfortunately, Samba 4.7.x is also affected by the problem I wrote about in the handbook (see here). The command
fails due to a regession that was introduced during development. More information can be acquired from this conversation on samba-technical.
Since this is a problem in Samba, I cannot fix it in Smb4K. There are actually three routes to make Smb4K work probperly again:
Last edit: Alexander Reinholdt 2018-08-17