DNS forwarding and failure to bind for port 137

Dewayne dewayne.geraghty at heuristicsystems.com.au
Tue Dec 4 01:35:24 MST 2012

Two challenges:

1. Following the guidance from the Samba wiki we have a working SAMBA4 AD operating within a FreeBSD jail. Unfortunately the
internal DNS isn't actually forwarding names/addresses for which it is not authoritative.  A tcpdump on the only interface used
captures the inbound request but not the forward, per the smb.conf dns forwarder.  Is this something peculiar to my situation? We
installed samba-4.0.0rc5 via tar file. 
2. I notice that nbtd starts when SAMBA4 runs within the host system but not within a jail. Truss provides some insight:
truss /usr/local/samba/sbin/samba -i -M single -d 2 
socket(PF_INET,SOCK_DGRAM,0)                     = 39 (0x27)
fcntl(39,F_GETFD,)                               = 0 (0x0)
fcntl(39,F_SETFD,FD_CLOEXEC)                     = 0 (0x0)
fcntl(39,F_GETFL,)                               = 2 (0x2)
fcntl(39,F_SETFL,O_NONBLOCK|0x2)                 = 0 (0x0)
setsockopt(0x27,0xffff,0x20,0x7fffffffd314,0x4,0x20) = 0 (0x0)
setsockopt(0x27,0xffff,0x4,0x7fffffffd2b4,0x4,0x4) = 0 (0x0)
bind(39,{ AF_INET },16)        ERR#49 'Can't assign requested address'
write(1,"Failed to bind to"...,71) = 71 (0x47)
close(39)                                        = 0 (0x0)
task_server_terminate: [nbtd failed to setup interfaces]
write(1,"task_server_terminate: [nbtd fai"...,57) = 57 (0x39)

I should note that FreeBSD within a jail requires these smb.conf settings:
        interfaces =  # The SAMBA4 servers IP
        bind interfaces only = yes

Is there anything that I can do to fix or provide more information?

Regards, Dewayne.

More information about the samba-technical mailing list