Laurence Vanek wrote:
I have a Samba server running on my small home network. The home
network is served off its own NIC (eth0). A separate NIC (eth1) is
connected thru cable modem to VOIP router. The VOIP router appears to
be doing NAT and serves up an address:
eth1 Link encap:Ethernet HWaddr 00:04:75:73:91:0F inet
addr:192.168.15.100 Bcast:192.168.15.255 Mask:255.255.255.0
inet6 addr: fe80::204:75ff:fe73:910f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:303755 errors:0 dropped:0 overruns:0 frame:0
TX packets:265877 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:326973694 (311.8 MiB) TX bytes:41058862 (39.1 MiB)
Interrupt:22 Base address:0x8000
My /var/log/messages file is filling with the following messages,
every 10-15 minutes:
==========
Apr 15 11:24:25 localhost nmbd[4279]: [2006/04/15 11:24:25, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_status_fail(488)
Apr 15 11:24:25 localhost nmbd[4279]:
get_domain_master_name_node_status_fail:
Apr 15 11:24:25 localhost nmbd[4279]: Doing a node status request to
the domain master browser at IP 192.168.15.100 failed.
Apr 15 11:24:25 localhost nmbd[4279]: Cannot get workgroup name.
==========
I can see my shares on the network from a Windows XP client. All
seems well. I have shared my linux box printer thru the printer share
& it works.
My testparm file:
==========
[global]
workgroup = MSHOME
netbios name = SAMBA
server string = Samba %v
interfaces = eth0
bind interfaces only = Yes
guest account = lvanek
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n
*ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*upda
ed*successfully*
username map = /etc/samba/smbusers
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = /etc/printcap
os level = 65
preferred master = Yes
domain master = Yes
dns proxy = No
wins support = Yes
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
guest ok = Yes
hosts allow = 192.168.1.
cups options = raw
[homes]
comment = Home Directories
path = /home/lvanek
valid users = lvanek
read only = No
directory mask = 0775
hide dot files = No
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[tmp]
comment = Temporary file space
path = /tmp
valid users = bvanek, lvanek
read only = No
===============
My take on the log messages is that nmbd broadcasts to ALL interfaces
even though I bind only to eth0 (home network NIC). The IP address
(192.168.15.100) is assigned by the VOIP router.
Any suggestions as to how I can quiet these?
As a side note, I am confused as to whether I need to call for Samba
to be a domain master in a simple setup like this. I appears as
though I do. Thoughts?
As suggested I set "wins support = no" which stopped the messages in the
log. My setup does not need this option. Also added "Samba" to my
/etc/hosts file to make sure we resolve, although this was not related
to problem.
Still curious as to how one would stop these messages if needed wins
support & had a setup like mine.
Thanks for help.
That's probably a question for a MCSE or someone who knows more about
setting up a Windoze network. I don't know why a Windoze network might
need wins support. Knowing Microsoft products, its probably some legacy
support option that typically doesn't matter for relatively current
products.
The setup I run has my Samba server running as the equivalent of a PDC.
At my previous employment, I needed this in order to test certain
aspects of their product. I'm maintaining it now more or less just so
I'm proficient at it. There are also some security considerations so,
as long as my wife keeps running Windoze, I'm stuck maintaining my
current configuration. Would love to get her onto Linux so I could
expunge Windoze from my network.
Cheers,
Dave
--
Politics, n. Strife of interests masquerading as a contest of principles.
-- Ambrose Bierce
