Thanks for the comment... Thought so too... especially one of the browser roles...
I guess the problem is in nmbd, as all the fuctionality of smbd is available... I've managed to join the computers specifying a wins server explicitly... I would have loved to put the wins server in dhcp, but there's no such option in ebox, and even though I could have edited the stub files directly, any update would have broken the hand made configuration...
Just in case you can give me some sort of clue, here's the nmbd log
There is already a domain master browser at IP 10.80.46.3 for workgroup MICSIED.LOCAL registered on subnet UNICAST_SUBNET.
[2009/05/11 10:17:59, 0] nmbd/nmbd_become_dmb.c:bec
become_domain_master_brows
Attempting to become domain master browser on workgroup MICSIED.LOCAL, subnet UNICAST_SUBNET.
[2009/05/11 10:17:59, 0] nmbd/nmbd_become_dmb.c:bec
become_domain_master_brows
[2009/05/11 10:17:59, 0] nmbd/nmbd_become_dmb.c:bec
become_domain_master_query
There is already a domain master browser at IP 10.80.46.3 for workgroup MICSIED.LOCAL registered on subnet UNICAST_SUBNET.
[2009/05/11 10:18:20, 0] nmbd/nmbd_browsesync.c:dom
domain_master_node_status_
Doing a node status request to the domain master browser
for workgroup MICSIED.LOCAL at IP 10.80.46.3 failed.
Cannot sync browser lists.
[2009/05/11 10:22:59, 0] nmbd/nmbd_become_dmb.c:bec
become_domain_master_brows
Attempting to become domain master browser on workgroup MICSIED.LOCAL, subnet UNICAST_SUBNET.
[2009/05/11 10:22:59, 0] nmbd/nmbd_become_dmb.c:bec
become_domain_master_brows
[2009/05/11 10:22:59, 0] nmbd/nmbd_become_dmb.c:bec
10.80.46.3 is actually my external ip address... I really don't know what's that doing there since samba is not listening on that interface...
Main Topics
Browse All Topics





by: lanboyoPosted on 2009-05-11 at 17:11:33ID: 24360178
You want to check the samba log files...
samba_directory /var/smbd.log and samba_directory /var/nmbd.log
Something hre may give you some assistance. Additionally since this occured during a reboot, someone may have grabbed the AD roles for the network in the servers absense.