nbtd netlogon handler failed from

[Kahle, Markus]

Hi there, 


after compiling latest samba4 master branch (4.0.0alpha15-GIT-850bf67) I've been running into some strange error messages. 


Starting samba via 'samba -i -M single -d3' the following error messages appears soon after: 


------------------------------- 

[...] 
nbtd netlogon handler failed from 10.0.11.16:138 to BEL-LOCAL<1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.11.16:138 to BEL-LOCAL<1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.11.12:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.11.12:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.1.2:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.1.2:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.1.3:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.1.3:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.11.16:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.11.16:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.11.12:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.11.12:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.0.11:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.0.11:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.1.3:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
nbtd netlogon handler failed from 10.0.1.3:138 to BEL-LOCAL <1c> - NT_STATUS_BAD_NETWORK_NAME 
[...] 
------------------------------- 


I've provisoned an AD with realm BEL.LOC and domain name BEL. 
BEL-LOCAL is my current active Samba3 (NT4) Domain in the same network/subnet. 
So why is it , that samba4 AD is getting connects from old NT4 Domain , even if Domain-Names are different ? 
This stuff is happening only in the lastest builds, tried a master branch build last week and there wasn't any kind of that error messages. 


-- 
Markus