[opensuse] Samba name server ... is now a local master browser
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After several config iterations I get this on my server (with samba): <3.3> 2017-12-19T11:07:38.329158+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:38.328633, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2) <3.3> 2017-12-19T11:07:38.329780+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:38.330184+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.330570+01:00 Isengard nmbd 6089 - - Samba server ISENGARD is now a domain master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:38.330972+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.331382+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:46.337276+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:46.337047, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) <3.3> 2017-12-19T11:07:46.337938+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:46.338347+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.338655+01:00 Isengard nmbd 6089 - - Samba name server ISENGARD is now a local master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:46.338980+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.339274+01:00 Isengard nmbd 6089 - - ***** That goes to the /var/log/warn file. Samba is too talkative on that log, at the spam level. Anyway. Why does it say: "subnet 192.168.1.16"? Should it not apply to the entire 192.168.1.* network? Related to this, on my desktop I get, continuosly: <3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - [2017/12/19 14:10:39.526400, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.14 for name VALINOR<1d>. <3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - This response was from IP 192.168.1.16, reporting an IP address of 192.168.1.16. <3.3> 2017-12-19 14:15:29 Telcontar nmbd 30623 - - [2017/12/19 14:15:29.806598, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-19 14:15:29 Telcontar nmbd 30623 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.14 for name VALINOR<1d>. <3.3> 2017-12-19 14:15:29 Telcontar nmbd 30623 - - This response was from IP 192.168.1.16, reporting an IP address of 192.168.1.16. Why does it say "Multiple responses?" <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - [2017/12/19 14:17:41.174696, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - find_domain_master_name_query_fail: <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - [2017/12/19 14:17:41.174830, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - find_domain_master_name_query_fail: <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to sync browse lists in this workgroup. Why doesn't Telcontar accept that Isengard is the master? I wouldn't care for those errors, except that they are spamming my warning log :-( Telcontar config: global] workgroup = VALINOR passdb backend = tdbsam local master = yes # preferred master = yes os level = 65 printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = No security = user wins support = Yes ldap admin dn = log level = 1 passdb:1 auth:1 winbind:1 #log level = 3 passdb:1 auth:1 winbind:1 Isengard (the server) config: global] workgroup = VALINOR passdb backend = tdbsam local master = yes os level = 70 printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = Yes security = user wins support = Yes # wins server = Yes ldap admin dn = - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo5FEcACgkQtTMYHG2NR9XmwgCfczHsW9dVlq/qtguytJd0rwVz zVAAni/NGmmR+w1QxW2l9ig4DGVJycKL =5JyF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/19/2017 07:29 AM, Carlos E. R. wrote:
Hi,
After several config iterations I get this on my server (with samba):
<3.3> 2017-12-19T11:07:38.329158+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:38.328633, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2) <3.3> 2017-12-19T11:07:38.329780+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:38.330184+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.330570+01:00 Isengard nmbd 6089 - - Samba server ISENGARD is now a domain master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:38.330972+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.331382+01:00 Isengard nmbd 6089 - - *****
<3.3> 2017-12-19T11:07:46.337276+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:46.337047, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) <3.3> 2017-12-19T11:07:46.337938+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:46.338347+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.338655+01:00 Isengard nmbd 6089 - - Samba name server ISENGARD is now a local master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:46.338980+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.339274+01:00 Isengard nmbd 6089 - - *****
You should only get this once on boot, or once when you start/stop samba on this (or any other box that can become a browsemaster)
Related to this, on my desktop I get, continuosly:
<3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - [2017/12/19 14:10:39.526400, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.14 for name VALINOR<1d>. <3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - This response was from IP 192.168.1.16, reporting an IP address of 192.168.1.16.
<snop>
Why does it say "Multiple responses?"
I only see this on clients running older 3X versions of samba. In environments where I have only samba 4.7X, I don't see these anymore (no change in name resolution otherwise) They are annoying.
<3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - [2017/12/19 14:17:41.174696, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - find_domain_master_name_query_fail: <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - [2017/12/19 14:17:41.174830, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - find_domain_master_name_query_fail: <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to sync browse lists in this workgroup.
Why doesn't Telcontar accept that Isengard is the master?
os level = 65 is pretty darn high and will win in default browse master elections. I know that the default has changed over the years and the recommended way at once was to set the os level = 66 to insure one box won the browse master election. You will need to check that Telcontar is set lower than Isengard for Telcontar to accept Isengard as the master. The finer details of the election fight will take a bit more research, but if you have an os level problem, that is where you will start. -- David C. Rankin, J.D.,P.E.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2017-12-19 at 18:58 -0600, David C. Rankin wrote:
On 12/19/2017 07:29 AM, Carlos E. R. wrote:
Hi,
After several config iterations I get this on my server (with samba):
<3.3> 2017-12-19T11:07:38.329158+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:38.328633, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2) <3.3> 2017-12-19T11:07:38.329780+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:38.330184+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.330570+01:00 Isengard nmbd 6089 - - Samba server ISENGARD is now a domain master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:38.330972+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.331382+01:00 Isengard nmbd 6089 - - *****
<3.3> 2017-12-19T11:07:46.337276+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:46.337047, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) <3.3> 2017-12-19T11:07:46.337938+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:46.338347+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.338655+01:00 Isengard nmbd 6089 - - Samba name server ISENGARD is now a local master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:46.338980+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.339274+01:00 Isengard nmbd 6089 - - *****
You should only get this once on boot, or once when you start/stop samba on this (or any other box that can become a browsemaster)
Yes, Isengard has kept silent since this morning. But why does it say "subnet 192.168.1.16"? Why not the entire 255 IPs? Why only one IP? I think that is the problem, that it is the master for a single IP, not the entire network.
Related to this, on my desktop I get, continuosly:
<3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - [2017/12/19 14:10:39.526400, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.14 for name VALINOR<1d>. <3.3> 2017-12-19 14:10:39 Telcontar nmbd 30623 - - This response was from IP 192.168.1.16, reporting an IP address of 192.168.1.16.
<snop>
Why does it say "Multiple responses?"
I only see this on clients running older 3X versions of samba. In environments where I have only samba 4.7X, I don't see these anymore (no change in name resolution otherwise) They are annoying.
Well, I have 4.4, the default on Leap 42.2. The problem is that they SPAM the WARN log. :-/
<3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - [2017/12/19 14:17:41.174696, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - find_domain_master_name_query_fail: <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - [2017/12/19 14:17:41.174830, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - find_domain_master_name_query_fail: <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-19 14:17:41 Telcontar nmbd 30623 - - Unable to sync browse lists in this workgroup.
Why doesn't Telcontar accept that Isengard is the master?
os level = 65
is pretty darn high and will win in default browse master elections. I know that the default has changed over the years and the recommended way at once was to set the os level = 66 to insure one box won the browse master election. You will need to check that Telcontar is set lower than Isengard for Telcontar to accept Isengard as the master. The finer details of the election fight will take a bit more research, but if you have an os level problem, that is where you will start.
Well, Isengard has 70, it is higher. I have set Telcontar now down to 64. Still same problem: <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - [2017/12/20 02:42:02.458199, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - [2017/12/20 02:42:02.458330, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 02:42:02 Telcontar nmbd 22138 - - Unable to sync browse lists in this workgroup. I set it to 30. Still same noise. :-( Can't I tell samba the exact IP of the master, and don't argue over it? - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo5wcMACgkQtTMYHG2NR9WYzACeIq+W+Zktok0bHEeEEqUe++PW FIMAnjrXmM5v5wHOHRL//83ylqvXKjTr =U1h+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/19/2017 07:49 PM, Carlos E. R. wrote:
I set it to 30. Still same noise. :-(
Can't I tell samba the exact IP of the master, and don't argue over it?
Sure, On Isengard (you want to win), set preferred master = Yes wins support = Yes On Telconstar, set wins server = 192.168.6.17 ; IP of Isengard -- David C. Rankin, J.D.,P.E.
On 2017-12-20 06:26, David C. Rankin wrote:
On 12/19/2017 07:49 PM, Carlos E. R. wrote:
I set it to 30. Still same noise. :-(
Can't I tell samba the exact IP of the master, and don't argue over it?
Sure,
On Isengard (you want to win), set
preferred master = Yes wins support = Yes
That was already set. local master = yes (I'll try "no") preferred master = yes wins support = Yes wins server = Yes
On Telconstar, set
wins server = 192.168.6.17 ; IP of Isengard
Nope, doesn't work. On Telcontar I did: preferred master = no wins support = Yes wins server = 192.168.6.16 ; IP of Isengard and still I get: <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - [2017/12/20 12:48:53.204728, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - [2017/12/20 12:48:53.204858, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 12:48:53 Telcontar nmbd 25191 - - Unable to sync browse lists in this workgroup. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 20/12/17 01:49, Carlos E. R. wrote:
After several config iterations I get this on my server (with samba):
<3.3> 2017-12-19T11:07:38.329158+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:38.328633, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2) <3.3> 2017-12-19T11:07:38.329780+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:38.330184+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.330570+01:00 Isengard nmbd 6089 - - Samba server ISENGARD is now a domain master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:38.330972+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:38.331382+01:00 Isengard nmbd 6089 - - *****
<3.3> 2017-12-19T11:07:46.337276+01:00 Isengard nmbd 6089 - - [2017/12/19 11:07:46.337047, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) <3.3> 2017-12-19T11:07:46.337938+01:00 Isengard nmbd 6089 - - ***** <3.3> 2017-12-19T11:07:46.338347+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.338655+01:00 Isengard nmbd 6089 - - Samba name server ISENGARD is now a local master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-19T11:07:46.338980+01:00 Isengard nmbd 6089 - - <3.3> 2017-12-19T11:07:46.339274+01:00 Isengard nmbd 6089 - - *****
You should only get this once on boot, or once when you start/stop samba on this (or any other box that can become a browsemaster)
Yes, Isengard has kept silent since this morning.
But why does it say "subnet 192.168.1.16"? Why not the entire 255 IPs? Why only one IP?
I think that is the problem, that it is the master for a single IP, not the entire network.
Clutching a bit at straws, but what are the equivalent messages on Telcontar? Telcontar is a member of VALINOR I assume :-) Are the smb.conf's similar? Can you do a diff and make sense of it? Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2017-12-20 at 16:08 -0000, Wols Lists wrote:
On 20/12/17 01:49, Carlos E. R. wrote:
...
Clutching a bit at straws, but what are the equivalent messages on Telcontar?
Telcontar is a member of VALINOR I assume :-)
Yep. This is Telcontar, the desktop machine (192.168.1.14): <3.3> 2017-12-20 12:57:43 Telcontar nmbd 25626 - - [2017/12/20 12:57:43.078817, 0] ../lib/util/become_daemon.c:124(daemon_ready) <3.3> 2017-12-20 12:57:43 Telcontar nmbd 25626 - - STATUS=daemon 'nmbd' finished starting up and ready to serve connections <3.6> 2017-12-20 12:57:43 Telcontar systemd 1 - - Started Samba NMB Daemon. <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - [2017/12/20 12:58:06.111442, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - ***** <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Samba name server TELCONTAR is now a local master browser for workgroup VALINOR on subnet 172.16.243.1 <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - ***** <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - [2017/12/20 12:58:06.111641, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - ***** <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Samba name server TELCONTAR is now a local master browser for workgroup VALINOR on subnet 192.168.1.14 <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - ***** <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - [2017/12/20 12:58:06.111731, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - ***** <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Samba name server TELCONTAR is now a local master browser for workgroup VALINOR on subnet 192.168.74.1 <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - ***** <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - [2017/12/20 12:58:06.111969, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - [2017/12/20 12:58:06.112024, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - [2017/12/20 12:58:06.112073, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Unable to sync browse lists in this workgroup. till now: <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - [2017/12/20 18:14:00.902867, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - [2017/12/20 18:14:00.903003, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - Unable to sync browse lists in this workgroup. <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - [2017/12/20 18:14:00.903056, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail) <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - find_domain_master_name_query_fail: <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - Unable to find the Domain Master Browser name VALINOR<1b> for the workgroup VALINOR. <3.3> 2017-12-20 18:14:00 Telcontar nmbd 25626 - - Unable to sync browse lists in this workgroup. Isengard, the server (192.168.1.16): <3.6> 2017-12-20T12:57:16.789998+01:00 Isengard systemd 1 - - Starting Samba NMB Daemon... <3.4> 2017-12-20T12:57:16.835681+01:00 Isengard systemd 1 - - nmb.service: Supervising process 20152 which is not our child. We'll most likely not notice when it exits. <3.3> 2017-12-20T12:57:16.837277+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:16.836947, 0] ../source3/nmbd/asyncdns.c:158(start_async_dns) <3.3> 2017-12-20T12:57:16.837940+01:00 Isengard nmbd 20152 - - started asyncdns process 20153 <3.3> 2017-12-20T12:57:16.840662+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:16.840492, 0] ../lib/util/become_daemon.c:124(daemon_ready) <3.3> 2017-12-20T12:57:16.841254+01:00 Isengard nmbd 20152 - - STATUS=daemon 'nmbd' finished starting up and ready to serve connections <3.6> 2017-12-20T12:57:16.841762+01:00 Isengard systemd 1 - - Started Samba NMB Daemon. <3.3> 2017-12-20T12:57:16.842273+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:16.840892, 0] ../source3/nmbd/nmbd_become_dmb.c:339(become_domain_master_browser_wins) <3.3> 2017-12-20T12:57:16.842762+01:00 Isengard nmbd 20152 - - become_domain_master_browser_wins: <3.3> 2017-12-20T12:57:16.843201+01:00 Isengard nmbd 20152 - - Attempting to become domain master browser on workgroup VALINOR, subnet UNICAST_SUBNET. <3.3> 2017-12-20T12:57:16.843638+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:16.841019, 0] ../source3/nmbd/nmbd_become_dmb.c:353(become_domain_master_browser_wins) <3.3> 2017-12-20T12:57:16.844107+01:00 Isengard nmbd 20152 - - become_domain_master_browser_wins: querying WINS server from IP 192.168.1.16 for domain master browser name VALINOR<1b> on workgroup VALINOR <3.3> 2017-12-20T12:57:21.511955+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:21.511777, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2) <3.3> 2017-12-20T12:57:21.512672+01:00 Isengard nmbd 20152 - - ***** <3.3> 2017-12-20T12:57:21.513108+01:00 Isengard nmbd 20152 - - <3.3> 2017-12-20T12:57:21.513465+01:00 Isengard nmbd 20152 - - Samba server ISENGARD is now a domain master browser for workgroup VALINOR on subnet UNICAST_SUBNET <3.3> 2017-12-20T12:57:21.513839+01:00 Isengard nmbd 20152 - - <3.3> 2017-12-20T12:57:21.514182+01:00 Isengard nmbd 20152 - - ***** <3.3> 2017-12-20T12:57:21.514520+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:21.512025, 0] ../source3/nmbd/nmbd_become_dmb.c:294(become_domain_master_browser_bcast) <3.3> 2017-12-20T12:57:21.514880+01:00 Isengard nmbd 20152 - - become_domain_master_browser_bcast: <3.3> 2017-12-20T12:57:21.515214+01:00 Isengard nmbd 20152 - - Attempting to become domain master browser on workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-20T12:57:21.515546+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:21.512113, 0] ../source3/nmbd/nmbd_become_dmb.c:307(become_domain_master_browser_bcast) <3.3> 2017-12-20T12:57:21.515874+01:00 Isengard nmbd 20152 - - become_domain_master_browser_bcast: querying subnet 192.168.1.16 for domain master browser on workgroup VALINOR <3.3> 2017-12-20T12:57:29.522005+01:00 Isengard nmbd 20152 - - [2017/12/20 12:57:29.521791, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2) <3.3> 2017-12-20T12:57:29.522669+01:00 Isengard nmbd 20152 - - ***** <3.3> 2017-12-20T12:57:29.523033+01:00 Isengard nmbd 20152 - - <3.3> 2017-12-20T12:57:29.523033+01:00 Isengard nmbd 20152 - - <3.3> 2017-12-20T12:57:29.523530+01:00 Isengard nmbd 20152 - - Samba server ISENGARD is now a domain master browser for workgroup VALINOR on subnet 192.168.1.16 <3.3> 2017-12-20T12:57:29.523858+01:00 Isengard nmbd 20152 - - <3.3> 2017-12-20T12:57:29.524234+01:00 Isengard nmbd 20152 - - ***** <3.3> 2017-12-20T13:02:24.882367+01:00 Isengard nmbd 20152 - - [2017/12/20 13:02:24.882115, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-20T13:02:24.883196+01:00 Isengard nmbd 20152 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.16 for name VALINOR<1d>. <3.3> 2017-12-20T13:02:24.883531+01:00 Isengard nmbd 20152 - - This response was from IP 192.168.1.14, reporting an IP address of 192.168.1.14. <3.3> 2017-12-20T13:07:35.181043+01:00 Isengard nmbd 20152 - - [2017/12/20 13:07:35.180746, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-20T13:07:35.182037+01:00 Isengard nmbd 20152 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.16 for name VALINOR<1d>. <3.3> 2017-12-20T13:07:35.182630+01:00 Isengard nmbd 20152 - - This response was from IP 192.168.1.14, reporting an IP address of 192.168.1.14. <10.6> 2017-12-20T13:10:01.047699+01:00 Isengard cron 20447 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.3> 2017-12-20T13:12:27.288620+01:00 Isengard nmbd 20152 - - [2017/12/20 13:12:27.288128, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-20T13:12:27.295771+01:00 Isengard nmbd 20152 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.16 for name VALINOR<1d>. <3.3> 2017-12-20T13:12:27.296335+01:00 Isengard nmbd 20152 - - This response was from IP 192.168.1.14, reporting an IP address of 192.168.1.14. <3.3> 2017-12-20T13:17:27.586706+01:00 Isengard nmbd 20152 - - [2017/12/20 13:17:27.586465, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-20T13:17:27.593382+01:00 Isengard nmbd 20152 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.16 for name VALINOR<1d>. <3.3> 2017-12-20T13:17:27.593977+01:00 Isengard nmbd 20152 - - This response was from IP 192.168.1.14, reporting an IP address of 192.168.1.14. <10.6> 2017-12-20T13:20:01.629578+01:00 Isengard cron 20706 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.3> 2017-12-20T13:22:38.876313+01:00 Isengard nmbd 20152 - - [2017/12/20 13:22:38.876035, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-20T13:22:38.883425+01:00 Isengard nmbd 20152 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.16 for name VALINOR<1d>. <3.3> 2017-12-20T13:22:38.883941+01:00 Isengard nmbd 20152 - - This response was from IP 192.168.1.14, reporting an IP address of 192.168.1.14. <10.6> 2017-12-20T13:25:01.901526+01:00 Isengard cron 20804 - - pam_unix(crond:session): session opened for user root by (uid=0) <3.3> 2017-12-20T13:27:36.885219+01:00 Isengard nmbd 20152 - - [2017/12/20 13:27:36.884981, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) <3.3> 2017-12-20T13:27:36.886082+01:00 Isengard nmbd 20152 - - query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.16 for name VALINOR<1d>. <3.3> 2017-12-20T13:27:36.886399+01:00 Isengard nmbd 20152 - - This response was from IP 192.168.1.14, reporting an IP address of 192.168.1.14. Also quite talkative. And most of this talk goes to the /var/log/warn, as if it were an emergency :-/
Are the smb.conf's similar? Can you do a diff and make sense of it?
Isengard config: [global] workgroup = VALINOR passdb backend = tdbsam local master = no preferred master = yes os level = 70 printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = Yes security = user wins support = Yes wins server = Yes ldap admin dn = Telcontar config: [global] workgroup = VALINOR # GONDOR passdb backend = tdbsam local master = yes ; tried also "no". preferred master = no os level = 30 printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = No security = user wins support = Yes wins server = 192.168.6.16 ; IP of Isengard ldap admin dn = There are some differences, yes. I have now set in telcontar "local master = no", and so far it is keeping silent :-? Maybe that was what was missing after setting "wins server = 192.168.6.16". I'll have to watch for a while. [...] Both machines are keeping quiet. Bingo! :-) However... I guess that the 172.16.243.1 network will not be happy about it (the virtual machines). [...] Right, my W10 VM does not see its host in "network". But it neither did before. However \\Telcontar\share keeps working, so it is acceptable. I will later have to try the Laptop in Windows mode. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo6n5sACgkQtTMYHG2NR9XqrQCdE3hfIcA5FTmWrbYrl9otF7v7 lvEAnA4HgxCREwHRVLUGCV6oYEW71T8u =flV/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/12/17 17:36, Carlos E. R. wrote:
However... I guess that the 172.16.243.1 network will not be happy about it (the virtual machines). [...] Right, my W10 VM does not see its host in "network". But it neither did before. However \\Telcontar\share keeps working, so it is acceptable.
I will later have to try the Laptop in Windows mode.
I guess that's the VM gateway not forwarding across networks... What I've done now with VirtualBox is selected the option so VB acts as a bridge, and my VMs reach out to my main DNS server (the router). If you're happy with your VMs being on the same network as your physical boxes, try that ... (Certainly it made my VM networking seem to work a lot better :-) Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/12/17 18:06, Wols Lists wrote:
On 20/12/17 17:36, Carlos E. R. wrote:
However... I guess that the 172.16.243.1 network will not be happy about it (the virtual machines). [...] Right, my W10 VM does not see its host in "network". But it neither did before. However \\Telcontar\share keeps working, so it is acceptable.
I will later have to try the Laptop in Windows mode.
I guess that's the VM gateway not forwarding across networks...
What I've done now with VirtualBox is selected the option so VB acts as a bridge, and my VMs reach out to my main DNS server (the router). If Whoops ... DHCP you're happy with your VMs being on the same network as your physical boxes, try that ...
(Certainly it made my VM networking seem to work a lot better :-)
Cheers, Wol
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2017-12-20 at 18:06 -0000, Wols Lists wrote:
On 20/12/17 17:36, Carlos E. R. wrote:
However... I guess that the 172.16.243.1 network will not be happy about it (the virtual machines). [...] Right, my W10 VM does not see its host in "network". But it neither did before. However \\Telcontar\share keeps working, so it is acceptable.
I will later have to try the Laptop in Windows mode.
I guess that's the VM gateway not forwarding across networks...
What I've done now with VirtualBox is selected the option so VB acts as a bridge, and my VMs reach out to my main DNS server (the router). If
Whoops ... DHCP you're happy with your VMs being on the same network as your physical boxes, try that ...
(Certainly it made my VM networking seem to work a lot better :-)
I like to keep my virtual machines protected from the outside :-) But sometimes it backfires. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo7p3EACgkQtTMYHG2NR9W40QCgg8KMmZeFl29AaMbJp+oqIj4r NbMAn2hki/mpjfDUkytMigqQggnlypE1 =MCNI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/21/2017 06:22 AM, Carlos E. R. wrote:
I like to keep my virtual machines protected from the outside :-)
But sometimes it backfires.
Ahah! That's the part of the puzzle I was missing. Yes, as Wol said, always set the VB network interface a "bridged". Otherwise, each host can talk, but not listen. That makes sense why the browse lists couldn't be synced. Glad you got it sorted. -- David C. Rankin, J.D.,P.E.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2017-12-22 at 01:31 -0600, David C. Rankin wrote:
On 12/21/2017 06:22 AM, Carlos E. R. wrote:
I like to keep my virtual machines protected from the outside :-)
But sometimes it backfires.
Ahah!
That's the part of the puzzle I was missing. Yes, as Wol said, always set the VB network interface a "bridged". Otherwise, each host can talk, but not listen. That makes sense why the browse lists couldn't be synced.
Glad you got it sorted.
Well, the guests can talk with the host, no problem. I often ssh from host to guest. I can connect from guest to a samba share on the host by name, so that is not clear cut. What does not happen is talking from the server on another machine to the virtual guests. I think, I have not tried. I could do some routing to have that happen if I wanted. Anyway, the host said sometimes: <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Samba name server TELCONTAR is now a local master browser for workgroup VALINOR on subnet 172.16.243.1 which is the virtual machines network (vmnet1). It also said: <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Samba name server TELCONTAR is now a local master browser for workgroup VALINOR on subnet 192.168.1.14 <3.3> 2017-12-20 12:58:06 Telcontar nmbd 25626 - - Samba name server TELCONTAR is now a local master browser for workgroup VALINOR on subnet 192.168.74.1 One is my home network, and the other one I don't know... ah, vmnet8. I could set up routing on other machines saying that the GW for vmnet* is on my desktop, if wanted. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo9AHAACgkQtTMYHG2NR9XSNgCggNfsFvJl9VfQ2fh4yjxR27B8 1YEAoIllH8D7JDw1XS3fxNutgNO/xtFI =mFTr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Carlos E. R. -
David C. Rankin -
Wols Lists