wins server = yes is set and the 172.17.1.50 address is the address of
the PDC. From a Windows client perspective the the domain is
functioning as expected. There is a Samba BDC and mulitple Win2008 R2
member servers in the domain.
Are they anything to be concerned about?
[2011/03/11 07:45:32.336148, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336288, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336372, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336417, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336479, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336536, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336575, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336613, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336671, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
[2011/03/11 07:45:32.336725, 2]
nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
wins_registration_timeout: WINS server 127.0.0.1 timed out
registering IP 172.17.1.50
Thanks
Mike
----------------------------------------------------------------
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
man smb.conf
wins server = <the ip address of the wins server> (unneeded on the
actual wins server)
wins support = yes (on the actual wins server)
Sorry, I do have wins support = yes on the PDC. Faulty memory on my part.
----------------------------------------------------------------
Do you also have a "wins server = a.b.c.d" entry on the PDC? If so
remove it and restart Samba.
No.
PDC has
wins support = Yes
BDC has
wins server = 172.17.1.50
----------------------------------------------------------------
Is nmbd running on the PDC?
Do you have a wins.dat file (possible location of
/var/lib/samba/wins.dat - depends on configure)?
Maybe post the global section (minus comments) of your smb.conf.
Yes nmbd is running.
# ll /var/lib/samba/wins*
-rw-r--r-- 1 root root 4225 Mar 12 07:52 /var/lib/samba/wins.dat
-rw------- 1 root root 24576 Mar 12 07:52 /var/lib/samba/wins.tdb
# cat /etc/samba/smb.conf
[global]
unix charset = LOCALE
workgroup = example
netbios name = vm10
netbios aliases = filesshares
passdb backend = ldapsam:"ldap://vm10.example.co.nz"
username map = /etc/samba/smbusers
guest account = nobody
browseable = yes
log level = 2
syslog = 1
log file = /var/log/samba/%m
max log size = 0
obey pam restrictions = yes
name resolve order = wins bcast hosts
time server = Yes
shutdown script = /sbin/shutdown -h
abort shutdown script = /sbin/shutdown -c
logon script = logon.bat
logon path =
logon home =
domain master = Yes
local master = yes
preferred master = yes
os level = 65
domain logons = Yes
wins support = Yes
ldapsam:trusted = yes
ldapsam:editposix = yes
ldap ssl = off
ldap suffix = dc=example,dc=co,dc=nz
ldap machine suffix = ou=Computers,ou=Users
ldap user suffix = ou=People,ou=Users
ldap group suffix = ou=Groups
ldap admin dn = cn=sambaadmin,dc=example,dc=co,dc=nz
idmap backend = ldap:ldap://127.0.0.1
ldap idmap suffix = ou=Idmap
idmap uid = 10000-20000
idmap gid = 10000-20000
load printers = no
printing = bsd
printcap name = /dev/null
show add printer wizard = no
disable spoolss = yes
----------------------------------------------------------------
Sorry Mike, I don't have much of a clue.
There is a typo in your "name resolve order" - "hosts" should be
"host" but I doubt that has anything to do with the log entries.
Maybe a possibility is the use of "netbios aliases", as any aliases
will not be advertised as browse or logon servers the log entries may
just be informational, although I cannot reproduce the scenario here
with 3.5.8.
Chris
Chris
Thanks for looking any way. I have fixed "hosts", which isn't picked
up by testparm, and removed the alias and still get the messages.
Everything seems to working properly, or at least there are no
complaints from the users, so I guess I will ignore it for now.
Thanks
Mike
----------------------------------------------------------------
Testparm mostly tests the parameters (the left side of =) and not the arguments.
> I am seeing the following messages logged every 20 min on a Centos 5.5
> Samba 3.5.7 (SerNet RPMs) PDC.
>
(snip)
>
> [2011/03/11 07:45:32.336148, 2]
> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
> wins_registration_timeout: WINS server 127.0.0.1 timed out
> registering IP 172.17.1.50
Have you set "bind interfaces only = yes"?
Or have you set firewalls to prevent nmbd listening on 127.0.0.1?
Please show the result of "netstat -an | egrep '13[789]|445'".
---
TAKAHASHI Motonobu <mo...@monyo.com>
> From: Mike Brady <mike....@devnull.net.nz>
> Date: Fri, 11 Mar 2011 08:59:49 +1300
>
>> I am seeing the following messages logged every 20 min on a Centos 5.5
>> Samba 3.5.7 (SerNet RPMs) PDC.
>>
> (snip)
>>
>> [2011/03/11 07:45:32.336148, 2]
>> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
>> wins_registration_timeout: WINS server 127.0.0.1 timed out
>> registering IP 172.17.1.50
>
> Have you set "bind interfaces only = yes"?
> Or have you set firewalls to prevent nmbd listening on 127.0.0.1?
>
> Please show the result of "netstat -an | egrep '13[789]|445'".
>
> ---
> TAKAHASHI Motonobu <mo...@monyo.com>
>
"bind interfaces only = yes" is not set.
iptables has no rules loaded.
# iptables -L -v -n
Chain INPUT (policy ACCEPT 113M packets, 26G bytes)
pkts bytes target prot opt in out source
destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 82M packets, 112G bytes)
pkts bytes target prot opt in out source
destination
# netstat -an | egrep '13[789]|445'
tcp 0 0 :::139 :::*
LISTEN
tcp 0 0 :::445 :::*
LISTEN
tcp 0 0 ::ffff:172.17.1.50:445
::ffff:172.17.1.49:51292 ESTABLISHED
tcp 0 0 ::ffff:172.17.1.50:445
::ffff:172.17.1.88:1040 ESTABLISHED
tcp 0 0 ::ffff:172.17.1.50:139
::ffff:192.168.4.32:1854 ESTABLISHED
tcp 0 0 ::ffff:172.17.1.50:22
::ffff:172.17.7.6:53137 ESTABLISHED
tcp 0 0 ::ffff:172.17.1.50:445
::ffff:172.17.1.199:3387 ESTABLISHED
udp 0 0 172.17.1.255:137 0.0.0.0:*
udp 0 0 172.17.1.50:137 0.0.0.0:*
udp 0 0 0.0.0.0:137 0.0.0.0:*
udp 0 0 172.17.1.255:138 0.0.0.0:*
udp 0 0 172.17.1.50:138 0.0.0.0:*
udp 0 0 0.0.0.0:138 0.0.0.0:*
unix 2 [ ] DGRAM 283445
----------------------------------------------------------------
> Quoting TAKAHASHI Motonobu <mo...@monyo.com>:
>
> "bind interfaces only = yes" is not set.
>
> iptables has no rules loaded.
(snip)
> # netstat -an | egrep '13[789]|445'
(snip)
Umm...
Anyway I think it seems that you cannot connect to localhost:138/udp
from localhost...
How about SELinux?
Does "# setenforce 0" solve the problem?
---
TAKAHASHI Motonobu <mo...@monyo.com>
> From: Mike Brady <mike....@devnull.net.nz>
> Date: Wed, 16 Mar 2011 06:44:23 +1300
>
>> Quoting TAKAHASHI Motonobu <mo...@monyo.com>:
>>
>> "bind interfaces only = yes" is not set.
>>
>> iptables has no rules loaded.
>
> (snip)
>
>> # netstat -an | egrep '13[789]|445'
>
> (snip)
>
> Umm...
>
> Anyway I think it seems that you cannot connect to localhost:138/udp
> from localhost...
>
> How about SELinux?
>
> Does "# setenforce 0" solve the problem?
>
> ---
> TAKAHASHI Motonobu <mo...@monyo.com>
>
>
>
>
>
>
Nope. SELinux us in permissive mode. The box was kickstarted that way.
# sestatus
SELinux status: enabled
SELinuxfs mount: /selinux
Current mode: permissive
Mode from config file: permissive
Policy version: 21
Policy from config file: targeted
----------------------------------------------------------------