search for: nmbd_serverlistdb

Hi, I have a Samba 3 PDC running with around 20 Windows XP/2K clients. The PDC and the clients are in different subnets. I recently decided to add a Samba 3 BDC in the same subnet as the clients, to give some failover and also to reduce across-switch traffic. After creating the BDC, I restarted one of the clients but don't see it establishing connection with the BDC, instead it connects as

...eters in smb.conf Here are few lines of my system log which is giving more sensible hint: Jan 6 18:50:37 user-0ccet6p nmbd[13329]: write_browse_list: Can't open file /var/lib/samba/browse.dat.. Error was Permission denied Jan 6 18:50:37 user-0ccet6p nmbd[13329]: [2007/01/06 18:50:37, 0] nmbd/nmbd_serverlistdb.c:write_browse_list(339) Jan 6 18:50:37 user-0ccet6p kernel: audit(1168127437.054:524): avc: denied { search } for pid=13329 comm="nmbd" name="lib" dev=dm-0 ino=72220674 scontext=root:system_r:nmbd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_lib_t:s0 tclass=dir Jan 6 18:50:3...

...idmap config DMYDOM : range = 10000-99999 template shell = /bin/bash template homedir = /home/%U usershare allow guests = yes vfs objects = acl_xattr map acl inherit = yes [disk0] path ... ==> log.nmbd <== [2024/03/16 15:01:28.050958, 0] ../../source3/nmbd/nmbd_serverlistdb.c:342(write_browse_list) write_browse_list: Fatal error - cannot find my workgroup DMYDOM [2024/03/16 15:01:38.059448, 0] ../../source3/nmbd/nmbd_serverlistdb.c:342(write_browse_list) write_browse_list: Fatal error - cannot find my workgroup DMYDOM [2024/03/16 15:01:48.066835, 0] ../../source...

...name __SAMBA__<00> with first IP 172.16.1.1 ttl=0 nb_flags=40 to subnet 172.16.1.1 [1999/06/27 14:24:04, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(261) initiate_myworkgroup_startup: preferred master startup for workgroup LGST on subnet 172.16.1.1 [1999/06/27 14:24:04, 3] nmbd/nmbd_serverlistdb.c:create_server_on_workgroup(173) create_server_on_workgroup: Created server entry SERVER of type 40019a03 (Samba Server) on workgroup LGST. [1999/06/27 14:24:04, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(289) initiate_myworkgroup_startup: Added server name entry SERVER on subnet...

...send_local_master_announcement: type 8c9b0b for name MYDOMAIN on subnet 192.168.1.254 for workgroup MYDOMAIN [2009/03/07 10:26:23, 3] nmbd/nmbd_sendannounce.c:send_workgroup_announcement(185) send_workgroup_announcement: on subnet 192.168.1.254 for workgroup MYDOMAIN [2009/03/07 10:26:43, 3] nmbd/nmbd_serverlistdb.c:write_browse_list(419) write_browse_list: Wrote browse list into file /var/cache/samba/browse.dat [2009/03/07 10:26:49, 3] nmbd/nmbd_incomingdgrams.c:process_host_announce(117) process_host_announce: from HENRIQUE<00> IP 192.168.1.100 to MYDOMAIN<1d> for server HENRIQUE. [2009/03/...

...subnet 192.168.1.254: netmask= 255.255.255.0: WORKGROUP(1) current master browser = ANUBIS ANUBIS 408c9a03 (anubis server) WLADEK 40011003 () At this point Wladek is on the list (most other entries removed by me of course). [2010/03/23 11:34:13, 3] nmbd/nmbd_serverlistdb.c:expire_servers(195) expire_old_servers: Removing timed out server WLADEK A few seconds later wladek gets removed. [2010/03/23 11:34:13, 4] nmbd/nmbd_workgroupdb.c:dump_workgroups(281) dump_workgroups() dump workgroup on subnet 192.168.1.254: netmask= 255.255.255.0: WORKGROUP(...

...process_host_announce: from BYTER<00> IP 192.168.1.2 to MAGEX<1d> for server BYTER. When the clinets get the ip addresses via dhcp, then the announce cancelled and about a half hour later the clinets are dissapearing from the brows list. In the log: [2006/01/01 00:01:31, 3] nmbd/nmbd_serverlistdb.c:expire_servers(212) expire_old_servers: Removing timed out server BYTER If somebody know anything about this problem, I'm looking forward to the solution. Thank You. samba verison: 3.0.14a-3sarge -- Hohl Laszlo

...__SAMBA__<00> with first IP 192.168.1.1 ttl=0 nb_flags= 0 to subnet 192.168.1.1 [2001/03/11 16:18:01, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(244) initiate_myworkgroup_startup: preferred master startup for workgroup SYSTEM on subnet 192.168.1.1 [2001/03/11 16:18:01, 3] nmbd/nmbd_serverlistdb.c:create_server_on_workgroup(173) create_server_on_workgroup: Created server entry DAEMON of type 40019a03 (Samba 2.0.7 [daemon]) on workgroup SYSTEM. [2001/03/11 16:18:01, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(273) initiate_myworkgroup_startup: Added server name entry DAEMON...

...nfo(1934) call_trans2qfilepathinfo: SMB_VFS_STAT of ??T?\200\205 failed (No such file or directory) Here's part of log.nmbd. The client machine at issue here is at 10.1.1.30: [2004/05/18 10:26:21, 3] nmbd/nmbd_serverlistdb.c:write_browse_list(421) write_browse_list: Wrote browse list into file /var/cache/samba3/browse.dat [2004/05/18 10:26:48, 3] nmbd/nmbd_processlogon.c:process_logon_packet(278) process_logon_packet: SAMLOGON sidsize 0 ntv 11 [2004/05/18 10:26:48, 3] nmbd/nmbd_processlogon.c:process_logon_packet...

...se, configuration or log files can be provided if helpful - there are just too many files on two machines, so I'd rather post what ever seems to be helpful. The only log message I consider relevant right now is in log.nmbd on the fileserver: | [2019/06/13 19:14:02.586604, 0] | ../source3/nmbd/nmbd_serverlistdb.c:340(write_browse_list) | write_browse_list: Fatal error - cannot find my workgroup | SAMDOM But again, googling this did not enlighten me, escpecially as: | root at herakles:~# net ads workgroup | Workgroup: SAMDOM | root at fileserver:~# net ads testjoin | Join is OK Any hints are welcome...

...; with first IP 192.168.0.4 ttl=0 nb_flags= 0 to subnet 192.168.0.4 [2006/12/09 22:36:31, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(236) add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 192.168.0.4 ttl=0 nb_flags= 0 to subnet 192.168.0.4 [2006/12/09 22:36:31, 3] nmbd/nmbd_serverlistdb.c:create_server_on_workgroup(159) create_server_on_workgroup: Created server entry FAMILY of type 40019a03 (Linux Box) on workgroup UMEHARA. [2006/12/09 22:36:31, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(267) initiate_myworkgroup_startup: Added server name entry FAMILY on subne...

...3 (Mac01) | RNP002673E572C4 40000203 () | [2019/06/14 06:04:22.007420, 4] ../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet) | find_workgroup_on_subnet: workgroup search for SAMDOM on subnet 192.168.1.13: not found. | [2019/06/14 06:04:22.007432, 0] ../source3/nmbd/nmbd_serverlistdb.c:340(write_browse_list) | write_browse_list: Fatal error - cannot find my workgroup SAMDOM | [2019/06/14 06:04:22.007448, 4] ../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet) | find_workgroup_on_subnet: workgroup search for SAMDOM on subnet UNICAST_SUBNET: not found. | [2019/06...

...subnet: workgroup search for ENELPC on subnet 192.168.7.1: found. [2011/05/06 20:04:13.853985, 10] nmbd/nmbd_sendannounce.c:381(announce_myself_to_domain_master_browser) announce_myself_to_domain_master_browser: t (1304705053) - last(1304704509) < 900 [2011/05/06 20:04:13.854018, 3] nmbd/nmbd_serverlistdb.c:195(expire_servers) expire_old_servers: Removing timed out server BARTEKR [2011/05/06 20:04:13.854045, 4] nmbd/nmbd_workgroupdb.c:281(dump_workgroups) dump_workgroups() dump workgroup on subnet 192.168.7.1: netmask= 255.255.255.0: <---->ENELPC(1) current master browser =...

..._<00> with first IP 192.168.1.100 ttl=0 nb_flags=60 to subnet 192.168.1.100 [2009/06/05 17:33:17, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(245) initiate_myworkgroup_startup: preferred master startup for workgroup WORKGROUP on subnet 192.168.1.100 [2009/06/05 17:33:17, 3] nmbd/nmbd_serverlistdb.c:create_server_on_workgroup(157) create_server_on_workgroup: Created server entry UBUNTU of type 40819a0b (ubuntu server (Samba, Ubuntu)) on workgroup WORKGROUP. [2009/06/05 17:33:17, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(265) initiate_myworkgroup_startup: Added server name e...

...with first IP 172.60.1.107 ttl=0 nb_flags= 0 to subnet 172.60.1.107 [1999/09/02 14:24:37, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(250) add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 172.60.1.107 ttl=0 nb_flags= 0 to subnet 172.60.1.107 [1999/09/02 14:24:37, 3] nmbd/nmbd_serverlistdb.c:create_server_on_workgroup(173) create_server_on_workgroup: Created server entry TRUPROXY of type 40019a03 (Samba 2.0.0) on workgroup test. [1999/09/02 14:24:37, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(289) initiate_myworkgroup_startup: Added server name entry TRUPROXY on subne...

...RNP002673E572C4 40000203 () > | [2019/06/14 06:04:22.007420, 4] ../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet) > | find_workgroup_on_subnet: workgroup search for SAMDOM on subnet 192.168.1.13: not found. > | [2019/06/14 06:04:22.007432, 0] ../source3/nmbd/nmbd_serverlistdb.c:340(write_browse_list) > | write_browse_list: Fatal error - cannot find my workgroup SAMDOM > | [2019/06/14 06:04:22.007448, 4] ../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet) > | find_workgroup_on_subnet: workgroup search for SAMDOM on subnet UNICAST_SUBNET: not fo...

...! After a few hours running the nmbd is shutting down: Log is as follows: ---snipp--- [2003/10/26 05:00:48, 2] nmbd/nmbd_browsesync.c:sync_with_dmb(151) sync_with_dmb: Initiating sync with domain master browser DS9<20> at IP 192.168.0.1 for workgroup NCC1701 [2003/10/26 05:01:08, 3] nmbd/nmbd_serverlistdb.c:write_browse_list(421) write_browse_list: Wrote browse list into file /var/cache/samba/browse.dat [2003/10/26 05:02:38, 2] lib/interface.c:add_interface(79) added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0 [2003/10/26 05:02:38, 2] lib/interface.c:interpret_interface(128) c...

h>From: samba-request@lists.samba.org >Reply-To: samba@lists.samba.org >To: samba@lists.samba.org >Subject: samba Digest, Vol 34, Issue 14 >Date: Mon, 10 Oct 2005 12:05:06 +0000 (GMT) ------------------------------------------------------------------------------------------------------- From: Liu, Hong Quan ÁõºìȪ <liuhongquan@nwbsc.com> To: <samba@lists.samba.org>

...s can be provided if helpful - > there are just too many files on two machines, so I'd rather post > what ever seems to be helpful. The only log message I consider > relevant right now is in log.nmbd on the fileserver: > > | [2019/06/13 19:14:02.586604, 0] > | ../source3/nmbd/nmbd_serverlistdb.c:340(write_browse_list) > | write_browse_list: Fatal error - cannot find my workgroup > | SAMDOM > > But again, googling this did not enlighten me, escpecially as: > > | root at herakles:~# net ads workgroup > | Workgroup: SAMDOM > | root at fileserver:~# net ads testjo...

...__SAMBA__<00> with first IP 192.168.1.1 ttl=0 nb_flags= 0 to subnet 192.168.1.1 [2001/03/11 16:18:01, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(244) initiate_myworkgroup_startup: preferred master startup for workgroup SYSTEM on subnet 192.168.1.1 [2001/03/11 16:18:01, 3] nmbd/nmbd_serverlistdb.c:create_server_on_workgroup(173) create_server_on_workgroup: Created server entry DAEMON of type 40019a03 (Samba 2.0.7 [daemon]) on workgroup SYSTEM. [2001/03/11 16:18:01, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(273) initiate_myworkgroup_startup: Added server name entry DAEMON...