samba won't become local master browser (broadcast address problem... included smb.conf)
DeadComposer
approximately 7 computers as a means of coordinating workgroup login
passwords on each in my lab on my university campus. originally i
used a linksys wireless router in gateway mode with its dhcp server
enabled and everything worked magnificently when all the computers
were behind this wireless gateway. i then decided that it would be
better to open everything up and use the wireless router as a switch
because there were other computers beyond the uplink cable that were
using windows filesharing that i wanted to access as well. i then
proceeded to do this and now it seems that netbios name resolution is
completely screwed up. i have domain master = yes, local master =
yes, preferred master = yes, and os level = 255 all set in my smb.conf
file which i will attach later in this post. nmblookup no longer
resolves ANY name, each time giving me the error
querying main on 128.255.71.255
Packet send failed to 128.255.71.255(137) ERRNO=Host is down
name_query failed to find name main
findsmb and smbtree either give me a similar error or a completely
blank response. in addition, i noticed by running the smbclient -L
<hostname> on several hosts (whose names i can resolve only due to the
fact that they have my samba server set as their WINS server) that my
samba server never wins the local master browser election in spite of
the fact that it is set to do this. i have even tried manually
running
smbcontrol nmbd force-election
and this still results in samba not being elected. i have numerous
lines in my log.nmbd that say
[2004/06/20 18:06:39, 0] nmbd/nmbd_nameregister.c:register_name(512)
register_name: Failed to send packet trying to register name
^A^B__MSBROWSE__^B<01>
i am definitely at a loss to figure out why the standard C class
subnet's broadcast address (128.255.71.255) isn't working. i have
already consulted the network administrators for the university and
they said that they would have to mess with things to get them to work
but that the subnet on which these computers dwell is indeed a
standard subnet and the broadcast address should be correct. there
are also several lines saying the following (of course)
[2004/06/20 18:11:51, 0] libsmb/nmblib.c:send_udp(788)
Packet send failed to 128.255.71.255(138) ERRNO=Host is down
as i said earlier, everything worked correctly when i had the machines
behind the router with the dhcp server running. previously i had
installed FreeBSD on the machine while it was connected to the
wireless router's subnet (192.168.1), i realized that this was leading
to some inconsistencies among network configuration files so i decided
not to even mess with manually reconfiguring this and i reinstalled
the FreeBSD OS again while the machine was connected to the wide
subnet (128.255.71). this clearly didn't solve the problem. i also
tried installing Samba 2.2.9... same issue, nmblookup fails and it
still can't connect to the broadcast address. i also cleared the
browse.dat and wins.dat files several times but to no avail.
however, i see in the log.nmbd
[2004/06/19 15:27:27, 0]
nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113)
*****
Samba server BACKUP is now a domain master browser for workgroup
MURLAB on subnet 128.255.71.113
*****
so i know that the samba server is indeed becoming the domain master
browser though the broadcast address won't allow it to register the
__MSBROWSE__ name so that it can become the local master browser.
problem summary:
1. Samba 3.0.4 won't become local master browser though it seems to
become domain master browser.
2. nmblookup and other binaries that use nmblookup will not resolve
names (even when the name resolve order is set differently in the
smb.conf)
need help here... this is really cryptic.
smb.conf (not including shared... testparm shows not errors) :
[global]
workgroup = MURLAB
netbios name = BACKUP
encrypt passwords = yes
domain master = yes
local master = yes
preferred master = yes
os level = 255
security = user
domain logons = yes
wins support = yes
logon path = \\%L\profiles\%u
logon script = logon.bat
logon drive = H:
remote announce = 128.255.71.255
socket options = TCP_NODELAY SO_SNDBUF=8192
thanks,
Ryan
Robert E A Harvey
> os level = 255
I'm not too sure myself, I had all sorts of problems recently. In my
case the last XP machine connected was always the master. Rather
different from your problem of having no master, of course!
The only thing I can see is that it might be worth trying os level =
100 or something. 255 might have some special meaning, and it's not
impossible that anything >128 is seen as signed byte, and hence
negative. That's just a guess.
The documentation suggests that setting it to 20 means it would always
win. I escallated mine to 80, and that seemed to resolve everything,
or at least everything I could bring myself to care about after days
of it.
My original problem seemd to be a default installation of samba on
another machine that did not need to be there at all. I gave up on
trying to stop people's private XP machines becoming the master when
they plugged them in, as the network didn't seem to mind and coped
well enough when they were unplugged again. Sometimes things are too
broken to fix.
DeadComposer
because i recently installed a mandrake 9.2 binary of samba 3.0.2a and
set my os level to 255 and had absolutely no trouble. another problem
i have been having is the the IPC$ doesn't seem to work... checked the
log file for smbd and it shows attempted connections to /root/tmp...
why this is is beyond me. i see other people with the same problem.
i figured it was just a misconfiguration that occurred while running
configure in the src directory. i don't know how to preven it. that
seems to be ther bigger problem. but as i said, everything worked
beautifully as soon as i installed from binary. there must be a bug
in the configure script for 3.0.4. let me know if you know anything!
robert...@my-deja.com (Robert E A Harvey) wrote in message news:<5acbdcbf.04062...@posting.google.com>...