Unable to start Samba4/AD Domain Controller

[Neek]

Hi,

A while ago I managed to get a domain controller to run on my FreeNAS 9.3 box. I remember having some difficulty caused by DNS settings but eventually got it to work. I recently changed my router/firewall/DNS/DHCP from a cheapo box running DD-WRT to an x86 box running pfSense. As part of that change I had to move my subnet.

I am now unable to get the Services -> Domain Controller to start. The errors in the log.samba:

Code:

Mar 24 19:12:08 vault samba[47692]: [2016/03/24 19:12:08.884847, 0] ../source4/nbt_server/interfaces.c:205(nbtd_add_socket)
Mar 24 19:12:08 vault samba[47692]: Failed to bind to 192.168.1.255:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
Mar 24 19:12:08 vault samba[47692]: [2016/03/24 19:12:08.885144, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
Mar 24 19:12:08 vault samba[47692]: task_server_terminate: [nbtd failed to setup interfaces]
Mar 24 19:12:08 vault samba[47671]: [2016/03/24 19:12:08.896792, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Mar 24 19:12:08 vault samba[47671]: STATUS=daemon 'samba' finished starting up and ready to serve connectionssamba_terminate: nbtd failed to setup interfaces

So, can anyone point me at ways to get more details about what's still wrong? Is there a way to backup / text dump my old AD database, in case I have to recreate my users/SIDs, etc.?

I get this message when CIFS is running and when it is not. I can confirm that no other services are using port 137, and the fact that it's hitting the broadcast address for my network (192.168.1.0/24) seems correct, according to what I can see elsewhere online. I've noticed two things which might be relevant:

1. The latest version of Samba on samba.org appears to be 4.4.0. FreeNAS 9.3 is currently using Samba 4.1.21
2. According to this FreeBSD forum link, nbtd is not needed, but it's causing this fatal error for me.

Any help greatly appreciated!! Thanks!

 

[dlavigne]

Were you able to make any progress with this?

 

[Neek]

No, I can't figure out what else to do. Haven't found anything else at samba's mailing lists nor elsewhere. I'm stuck.

 

[Neek]

Strangely, I had to reinstall to new USB media today, and since restoring my config to the new USB media, AD is able to start without issues. There must have been some junk leftover from one of several failed updates to my boot drive, or something similar.