I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this
service to our existing Samab DC DOMAIN using samba-tool domain join. This
worked as far as I can tell.
I have these entries in smb4.conf
# BOF
# Global parameters
[global]
netbios name = SAMBA-02
realm = BROCKLEY-2016.HARTE-LYNE.CA
server role = active directory domain controller
workgroup = BROCKLEY-2016
interfaces = em0 localhost 192.168.8.66/24
bind interfaces only = yes
[sysvol]
path = /var/db/samba4/sysvol
read only = No
[netlogon]
path = /var/db/samba4/sysvol/brockley-2016.harte-lyne.ca/scripts
read only = No
# EOF
When I start samba_server this is what I get in /var/log/messages
May 5 15:13:12 samba-02 samba[37570]: [2020/05/05 15:13:12.448309, 0]
../../source4/smbd/server.c:587(binary_smbd_main)
May 5 15:13:12 samba-02 samba[37570]: samba version 4.10.13 started.
May 5 15:13:12 samba-02 samba[37570]: Copyright Andrew Tridgell and the
Samba Team 1992-2019
May 5 15:13:12 samba-02 samba[37571]: [2020/05/05 15:13:12.742041, 0]
../../source4/smbd/server.c:773(binary_smbd_main)
May 5 15:13:12 samba-02 samba[37571]: binary_smbd_main: samba: using
'standard' process model
May 5 15:13:12 samba-02 samba[37578]: [2020/05/05 15:13:12.765718, 0]
../../source4/nbt_server/interfaces.c:228(nbtd_add_socket)
May 5 15:13:12 samba-02 samba[37578]: Failed to bind to 192.168.8.66:137 -
NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
May 5 15:13:12 samba-02 samba[37578]: [2020/05/05 15:13:12.766128, 0]
../../source4/smbd/service_task.c:36(task_server_terminate)
May 5 15:13:12 samba-02 samba[37578]: task_server_terminate:
task_server_terminate: [nbtd failed to setup interfaces]
May 5 15:13:12 samba-02 samba[37571]: [2020/05/05 15:13:12.807896, 0]
../../lib/util/become_daemon.c:136(daemon_ready)
May 5 15:13:12 samba-02 samba[37571]: daemon_ready: daemon 'samba'
finished
starting up and ready to serve connections
May 5 15:13:12 samba-02 samba[37571]: [2020/05/05 15:13:12.820106, 0]
../../source4/smbd/server.c:371(samba_terminate)
May 5 15:13:12 samba-02 samba[37571]: samba_terminate: samba_terminate of
samba 37571: nbtd failed to setup interfaces
Before starting samba_server there are no listening processes. SO, whatever is
attached to 137 was caused by samba_server itself. Am I missing something
obvious here?
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
On 05/05/2020 20:23, James B. Byrne via samba wrote:> I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this > service to our existing Samab DC DOMAIN using samba-tool domain join. This > worked as far as I can tell. > > I have these entries in smb4.conf > > # BOF > # Global parameters > [global] > netbios name = SAMBA-02 > realm = BROCKLEY-2016.HARTE-LYNE.CA > server role = active directory domain controller > workgroup = BROCKLEY-2016 > interfaces = em0 localhost 192.168.8.66/24 > bind interfaces only = yes > > [sysvol] > path = /var/db/samba4/sysvol > read only = No > > [netlogon] > path = /var/db/samba4/sysvol/brockley-2016.harte-lyne.ca/scripts > read only = No > # EOF > > When I start samba_server this is what I get in /var/log/messages > > > May 5 15:13:12 samba-02 samba[37570]: [2020/05/05 15:13:12.448309, 0] > ../../source4/smbd/server.c:587(binary_smbd_main) > May 5 15:13:12 samba-02 samba[37570]: samba version 4.10.13 started. > May 5 15:13:12 samba-02 samba[37570]: Copyright Andrew Tridgell and the > Samba Team 1992-2019 > May 5 15:13:12 samba-02 samba[37571]: [2020/05/05 15:13:12.742041, 0] > ../../source4/smbd/server.c:773(binary_smbd_main) > May 5 15:13:12 samba-02 samba[37571]: binary_smbd_main: samba: using > 'standard' process model > May 5 15:13:12 samba-02 samba[37578]: [2020/05/05 15:13:12.765718, 0] > ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) > May 5 15:13:12 samba-02 samba[37578]: Failed to bind to 192.168.8.66:137 - > NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > May 5 15:13:12 samba-02 samba[37578]: [2020/05/05 15:13:12.766128, 0] > ../../source4/smbd/service_task.c:36(task_server_terminate) > May 5 15:13:12 samba-02 samba[37578]: task_server_terminate: > task_server_terminate: [nbtd failed to setup interfaces] > May 5 15:13:12 samba-02 samba[37571]: [2020/05/05 15:13:12.807896, 0] > ../../lib/util/become_daemon.c:136(daemon_ready) > May 5 15:13:12 samba-02 samba[37571]: daemon_ready: daemon 'samba' finished > starting up and ready to serve connections > May 5 15:13:12 samba-02 samba[37571]: [2020/05/05 15:13:12.820106, 0] > ../../source4/smbd/server.c:371(samba_terminate) > May 5 15:13:12 samba-02 samba[37571]: samba_terminate: samba_terminate of > samba 37571: nbtd failed to setup interfaces > > Before starting samba_server there are no listening processes. SO, whatever is > attached to 137 was caused by samba_server itself. Am I missing something > obvious here?Well, 137 is the netbios name service, so are you starting nmbd manually ? The other possibility are these lines in smb.conf: ??? interfaces = em0 localhost 192.168.8.66/24 ??? bind interfaces only = yes Try commenting them out. Rowland