The Samba-Bugzilla – Bug 12061
Last modified: 2017-01-09 18:59:11 UTC
+++ This bug was initially created as a clone of Bug #11849 +++
I'm not sure, but I think that the version of the patch that is currently already checked in broke something.
I'm used to do discovery of local devices like that:
smbclient -N -L localhost
Then look for the master of the workgroup (let's say BIGMASTER) and do:
smbclient -N -L BIGMASTER
Created attachment 12393 [details]
Trace of a good and a broken smbclient
Sorry for the long delay to generate the traces.
Following the discussion on #11849, here are the requested logs.
Test 1 and 2 are done with an unmodified version of Samba 4.2.12.
Test 3 is done with a modified version where I reverted the second part of the following patch:
"R4-BACKUP-1" is the client performing the request.
"5BIGBACKUPSOFT" is the device target that present the issue.
"LINKSYS08959" (not important), it is the network router, that is now the master of the isolated network.
I don't think that the "Test2" will be relevant anymore as I had to change of network for an isolated one to generate the traces but so the workgroup "master" changed to be the network router and not anymore the 5bigbackupsoft.
Let me know if there is something else that I can do to help you investigate this issue.
Is it possible for you to have a look at my traces to see if there could be something interesting inside them?
Do you have an idea for my issue, or do you need more info?