Hi, I have the same problem in Lucid. in "/etc/nsswitch.conf" I have (more important) =================== passwd: files ldap winbind group: files ldap winbind shadow: files ldap hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 wins networks: files dns =================== my smb.conf (from testparm output) ====================== [global] workgroup = MYDOMAIN realm = MYDOMAIN.COM server string = %h server (Servidor de Archivos - Samba %v, Ubuntu) security = ADS allow trusted domains = No obey pam restrictions = Yes password server = otherserver.mydomain.com log level = 2 log file = /var/log/samba/log.%m max log size = 1000 name resolve order = host wins bcast time server = Yes unix extensions = No printcap name = cups dns proxy = No wins server = 192.168.1.22 idmap uid = 10000-33554431 idmap gid = 10000-33554431 template shell = /bin/bash winbind enum users = Yes winbind enum groups = Yes invalid users = "@MYDOMAIN\equipos del dominio" admin users = admin_user cups options = raw wide links = Yes delete readonly = Yes dos filetime resolution = Yes fake directory create times = Yes ====================== and in the syslog, I have many errors from different daemons (samba, snmpd and ntp), but with "nss_wins" ident, for example: ================ nss_wins[XXX]: call_nt_transact_ioctl(0x90078): Currently not implemented. nss_wins[XXX]: check_usershare_stat: file /var/lib/samba/usershares/. owned by uid 0 is not a regular file nss_wins[XXX]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected) nss_wins[XXX]: /etc/snmp/snmpd.conf: line 3: Error: bad source address nss_wins[XXX]: gbahamonde (192.168.1.188) couldn't find service abastecimiento nss_wins[XXX]: getpeername failed. Error was Transport endpoint is not connected nss_wins[XXX]: last message repeated 2 times nss_wins[XXX]: last message repeated 3 times nss_wins[XXX]: last message repeated 4 times nss_wins[XXX]: libsmb/nmblib.c:834(send_udp) nss_wins[XXX]: lib/util_sock.c:1491(get_peer_addr_internal) nss_wins[XXX]: lib/util_sock.c:539(read_fd_with_timeout) nss_wins[XXX]: lib/util_sock.c:738(write_data) nss_wins[XXX]: nb-informatica (192.168.1.197) couldn't find service . nss_wins[XXX]: net-snmp: 1 error(s) in config file(s) nss_wins[XXX]: NET-SNMP version 5.4.2.1 nss_wins[XXX]: Packet send failed to 192.168.1.22(137) ERRNO=Network is unreachable nss_wins[XXX]: param/loadparm.c:8328(check_usershare_stat) nss_wins[XXX]: param/loadparm.c:8555(process_usershare_file) nss_wins[XXX]: param/loadparm.c:8569(process_usershare_file) nss_wins[XXX]: process_usershare_file: share name ::{2227a280-3aea-1069-a2de-XXXXXXXXX} contains invalid characters (any of %<>*?|/\+=;:",) nss_wins[XXX]: process_usershare_file: stat of /var/lib/samba/usershares/astecimiento failed. No such file or directory nss_wins[XXX]: process_usershare_file: stat of /var/lib/samba/usershares/nzalez failed. Permission denied nss_wins[XXX]: process_usershare_file: stat of /var/lib/samba/usershares/bholmes failed. Permission denied nss_wins[XXX]: process_usershare_file: stat of /var/lib/samba/usershares/arria failed. Permission denied nss_wins[XXX]: lbornoz (172.16.102.XXX) couldn't find service abilidad nss_wins[XXX]: lbornoz (172.16.102.XXX) couldn't find service plan_pub nss_wins[XXX]: read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. nss_wins[XXX]: read_fd_with_timeout: client 0.0.0.0 read error = Connection timed out. nss_wins[XXX]: Received TERM or STOP signal... shutting down... nss_wins[XXX]: smbd/nttrans.c:2119(call_nt_transact_ioctl) nss_wins[XXX]: smbd/process.c:62(srv_send_smb) nss_wins[XXX]: smbd/service.c:1202(make_connection) nss_wins[XXX]: xp-virtual (XXXXXXXX= couldn't find service ::{2227XX80-3aea-1069-a2de-08002b30309d} nss_wins[XXX]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer ================ If I restart the daemons (samba, ntp or snmp), so the syslog register the correct daemon in the ident field.. but, after reboot of machine the problem comeback and is necessary restart the daemons again. On previous Ubuntu version (9.10) this problem don't exists. and the problem is that logcheck, logwatch and other softwares relational with logs work wrong. thanks and attentive