[Samba] Error messages while managing groups in User Manager
I still haven't found any solution. Have anyone of you ever had this problem? I also tried it with tdbsam backend, and I got the same error, so it's not an LDAP-related issue. I have upgraded to Samba version 3.0.30, but the problem still exists. Please help, I'm out of ideas! My original message was: I recently set up a PDC using Samba version 3.0.28a. According to the official Samba documentation, I should be able to use the Microsoft User Manager tool to manage my Samba domain controller. I am able to add/delete/modify user accounts with no problem, but editing groups is not possible for some reason. For example, if I try to add a user account to a group, I get an Access denied error message. This sounds a bit strange to me, since I log in to the domain as root, so privilege problems should not happen. Is this a bug or have I misconfigured something? What I have already done: - Install Samba from package - Edit smb.conf to suit my needs - Create basic group mapping with the correct RIDs (512 for domain admins, 513 for users, 514 for guests) - Create a separated directory structure for all the shares My shares are located on separate partitions, each have the user_xattr option enabled in /etc/fstab. I attached my smb.conf file to this message, to make it easier to understand my configuration. Thanks for you help in advance! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba error messages
In my logs I see lots of the following error/warning messages: smbd[13953]: Denied connection from 136.201.157.55 (136.201.157.55) smbd[13968]: Denied connection from 0.0.0.0 (0.0.0.0) The first one is OK. It's a client thats been denied by the hosts.allow directive. What does the second one mean. Similarly in my log file directory I find two log files for each client -rw-r--r-- 1 root root 9292 Feb 20 12:49 log.10.50.44.36 -rw-r--r-- 1 root root 11492 Feb 21 17:03 log.cs304-36 Any reason why there are two. Finally I occasionally see lots of the following message: smbd[25037]: [2007/01/30 13:16:22, 0] smbd/service.c:make_connection(805) smbd[25037]: collinsj (136.201.24.94) couldn't find service fas$adm What is this service fas$adm. Samba is working fine so I assume that these are just warnings. Regards, Tony -- Tony Molloy. System Manager. Dept. of Comp. Sci. University of Limerick -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error Messages during installation
Hi, I installed of Samba on Debian GNU/Linux Sarge. Things went smoothly but I got some failed ( error? ) messages like account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0 at the end. Could someone please explain to me what this is. Is it a serious issue??? or problems with the deb package?? Full details below. Thankyou so much. Kind Regards - Vivek Varghese Cherian Free as in Freedom www.gnu.org wisdom:~# uname -a Linux wisdom.box 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux This is the error message that i am getting. Setting up samba (3.0.22-1) ... Generating /etc/default/samba... TDBSAM version too old (0), trying to convert it. TDBSAM converted successfully. account_policy_get: tdb_fetch_uint32 failed for field 1 (min password length), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 2 (password history), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to change password), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password age), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count minutes), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout attempt), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0 account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0 Starting Samba daemons: nmbd smbd. - -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Error Messages in /var/log/messages
Thanks for the information. The ports 139 and 445 are both open. Using SuSE 9.2 Professional. I guess I'll look more information on the FW and see what I can do. -Original Message- From: Craig White [mailto:[EMAIL PROTECTED] Sent: Thursday, February 09, 2006 11:50 PM To: samba@lists.samba.org Subject: Re: [Samba] Error Messages in /var/log/messages On Thu, 2006-02-09 at 16:08 -0500, Jesse Spangenberger wrote: Here's the output: Feb 9 15:51:26 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51248 DF PROTO=TCP SPT=1964 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2065 DF PROTO=TCP SPT=1136 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2066 DF PROTO=TCP SPT=1137 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:46 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:00:c5:fa:6d:6c:08:00 SRC=192.168.2.51 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=38844 DF PROTO=TCP SPT=2924 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204055C01010402) Feb 9 15:52:55 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:09:5b:e6:1a:27:08:00 SRC=192.168.1.254 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2068 DF PROTO=TCP SPT=1184 DPT=139 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:53:07 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:ca:86:d5:17:08:00 SRC=192.168.1.53 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=30142 DF PROTO=TCP SPT=2912 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2094 DF PROTO=TCP SPT=1138 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2095 DF PROTO=TCP SPT=1139 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:57 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:00:c5:fa:6d:6c:08:00 SRC=192.168.2.51 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=39419 DF PROTO=TCP SPT=2949 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204055C01010402) Feb 9 15:56:23 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51404 DF PROTO=TCP SPT=1967 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:56:55 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:09:5b:e6:1a:27:08:00 SRC=192.168.1.254 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2095 DF PROTO=TCP SPT=1186 DPT=139 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:57:07 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:ca:86:d5:17:08:00 SRC=192.168.1.53 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=30188 DF PROTO=TCP SPT=2915 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:01 SSI001 /usr/sbin/cron[3387]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Feb 9 15:59:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2123 DF PROTO=TCP SPT=1141 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2124 DF PROTO=TCP SPT=1140 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:get_peer_addr(1136) Feb 9 15:59:28 SSI001 smbd[3389]: getpeername failed. Error was Transport endpoint is not connected Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:get_peer_addr(1136) Feb 9 15:59:28 SSI001 smbd[3389]: getpeername failed. Error was Transport endpoint is not connected Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:write_socket_data(430) Feb 9 15:59:28
[Samba] Error Messages in /var/log/messages
Here's the output: Feb 9 15:51:26 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51248 DF PROTO=TCP SPT=1964 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2065 DF PROTO=TCP SPT=1136 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2066 DF PROTO=TCP SPT=1137 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:46 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:00:c5:fa:6d:6c:08:00 SRC=192.168.2.51 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=38844 DF PROTO=TCP SPT=2924 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204055C01010402) Feb 9 15:52:55 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:09:5b:e6:1a:27:08:00 SRC=192.168.1.254 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2068 DF PROTO=TCP SPT=1184 DPT=139 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:53:07 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:ca:86:d5:17:08:00 SRC=192.168.1.53 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=30142 DF PROTO=TCP SPT=2912 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2094 DF PROTO=TCP SPT=1138 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2095 DF PROTO=TCP SPT=1139 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:57 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:00:c5:fa:6d:6c:08:00 SRC=192.168.2.51 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=39419 DF PROTO=TCP SPT=2949 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204055C01010402) Feb 9 15:56:23 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51404 DF PROTO=TCP SPT=1967 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:56:55 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:09:5b:e6:1a:27:08:00 SRC=192.168.1.254 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2095 DF PROTO=TCP SPT=1186 DPT=139 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:57:07 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:ca:86:d5:17:08:00 SRC=192.168.1.53 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=30188 DF PROTO=TCP SPT=2915 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:01 SSI001 /usr/sbin/cron[3387]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Feb 9 15:59:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2123 DF PROTO=TCP SPT=1141 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2124 DF PROTO=TCP SPT=1140 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:get_peer_addr(1136) Feb 9 15:59:28 SSI001 smbd[3389]: getpeername failed. Error was Transport endpoint is not connected Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:get_peer_addr(1136) Feb 9 15:59:28 SSI001 smbd[3389]: getpeername failed. Error was Transport endpoint is not connected Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:write_socket_data(430) Feb 9 15:59:28 SSI001 smbd[3389]: write_socket_data: write failure. Error = Connection reset by peer Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:write_socket(455) Feb 9 15:59:28 SSI001 smbd[3389]: write_socket: Error writing 4 bytes to socket 43: ERRNO = Connection reset by peer Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:send_smb(647) Feb 9 15:59:28 SSI001 smbd[3389]: Error writing 4 bytes to client. -1. (Connection reset by peer) Feb 9 15:59:57 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT=
Re: [Samba] Error Messages in /var/log/messages
On Thu, 2006-02-09 at 16:08 -0500, Jesse Spangenberger wrote: Here's the output: Feb 9 15:51:26 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51248 DF PROTO=TCP SPT=1964 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2065 DF PROTO=TCP SPT=1136 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2066 DF PROTO=TCP SPT=1137 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:46 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:00:c5:fa:6d:6c:08:00 SRC=192.168.2.51 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=38844 DF PROTO=TCP SPT=2924 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204055C01010402) Feb 9 15:52:55 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:09:5b:e6:1a:27:08:00 SRC=192.168.1.254 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2068 DF PROTO=TCP SPT=1184 DPT=139 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:53:07 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:ca:86:d5:17:08:00 SRC=192.168.1.53 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=30142 DF PROTO=TCP SPT=2912 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2094 DF PROTO=TCP SPT=1138 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2095 DF PROTO=TCP SPT=1139 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:55:57 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:00:c5:fa:6d:6c:08:00 SRC=192.168.2.51 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=39419 DF PROTO=TCP SPT=2949 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (0204055C01010402) Feb 9 15:56:23 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51404 DF PROTO=TCP SPT=1967 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:56:55 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:09:5b:e6:1a:27:08:00 SRC=192.168.1.254 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2095 DF PROTO=TCP SPT=1186 DPT=139 WINDOW=16384 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:57:07 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:ca:86:d5:17:08:00 SRC=192.168.1.53 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=30188 DF PROTO=TCP SPT=2915 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:01 SSI001 /usr/sbin/cron[3387]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Feb 9 15:59:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2123 DF PROTO=TCP SPT=1141 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2124 DF PROTO=TCP SPT=1140 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:get_peer_addr(1136) Feb 9 15:59:28 SSI001 smbd[3389]: getpeername failed. Error was Transport endpoint is not connected Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:get_peer_addr(1136) Feb 9 15:59:28 SSI001 smbd[3389]: getpeername failed. Error was Transport endpoint is not connected Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:write_socket_data(430) Feb 9 15:59:28 SSI001 smbd[3389]: write_socket_data: write failure. Error = Connection reset by peer Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:write_socket(455) Feb 9 15:59:28 SSI001 smbd[3389]: write_socket: Error writing 4 bytes to socket 43: ERRNO = Connection reset by peer Feb 9 15:59:28 SSI001 smbd[3389]: [2006/02/09 15:59:28, 0] lib/util_sock.c:send_smb(647) Feb
[Samba] Error messages when trying to access a share
Hi everyone! Does anybody know what each of the error messages ERRinvnetname and ERRbadpw mean? The first one I get when I type my password after each of the following commands: smbclient -L localhost -U fabio //it only asks me for a password (I think it's to be my password) smbclient -L localhost -N //it doesn't ask a password. what/who is the username? The second one I get when I try this command: smbclient -L localhost //it does ask a password. but whatever password I type, the ERRbadpw error message arises on my screen. Why?? where does samba take a username for this password from? my smb.conf file is attached. you might want to take a look at it. -- Fabio Mendes Soares Computing Student (yet newbie at Samba) Ananindeua-PA-Brazil -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error messages every 32min after Win2k security update
I'm running Samba 3.0.10 from Debian Sarge (3.0.10-1). Samba is configured as the primary browse master for the network, and there are two windows boxes that access shares from the samba box, one win2k and the other XP Pro. Earlier this week, I installed a number of patches to the win2k box via windows update. I'm having trouble finding out exactly what patches were installed, but there are a stack of .log files with identical timestamps in my WINNT directory that might be the complete list: KB873339.log imsins.log KB885836.log comsetup.log iis5.log KB885835.log ocgen.log ockodak.log Ever since I installed those patches, I've been getting periodic errors in my samba logs. They occur every 32 minutes, but only when the Win2k machine is on: Jan 1 14:06:17 pyloric smbd[25844]: [2005/01/01 14:06:17, 0] lib/util_sock.c:get_peer_addr(1000) Jan 1 14:06:17 pyloric smbd[25844]: getpeername failed. Error was Transport endpoint is not connected Jan 1 14:06:17 pyloric smbd[25844]: [2005/01/01 14:06:17, 0] lib/util_sock.c:read_socket_data(384) Jan 1 14:06:17 pyloric smbd[25844]: read_socket_data: recv failure for 4. Error = Connection reset by peer I've googled for these error messages, and found a bunch of cases where people have them showing up quite frequently, and causing performance problems, but that doesn't seem to be the case here. I was able to trigger the same messages once on accessing a share from the win2k machine, but it didn't feel like my performance was impacted at all. One of the hits I found suggested that use sendfile might be causing this, but that's defaulting to off already in my install, so it's not the problem. Any idea what could be causing this, or what I could do to fix it? Thanks in advance, - Marc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error Messages
Hi list, after searching google and getting lost in to much results, maybe someone can explain me the meaning of some error-messages: 1. [2004/12/30 14:10:03, 2] smbd/sesssetup.c:setup_new_vc_session(608) setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources. 2. [2004/12/30 14:10:08, 0] passdb/pdb_ldap.c:ldapsam_search_one_group(2023) ldapsam_search_one_group: Problem during the LDAP search: LDAP error: (No such object) regards Arno -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Error Messages
Hi, On Dec 30, 2004, at 9:28 AM, Arno Seidel wrote: Hi list, after searching google and getting lost in to much results, maybe someone can explain me the meaning of some error-messages: 1. [2004/12/30 14:10:03, 2] smbd/sesssetup.c:setup_new_vc_session(608) setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources. According to what I know, this is not an error. It is just information. 2. [2004/12/30 14:10:08, 0] passdb/pdb_ldap.c:ldapsam_search_one_group(2023) ldapsam_search_one_group: Problem during the LDAP search: LDAP error: (No such object) This means that the group you are intending to login as does not exist in your LDAP tree. When does this happen. Can you give some background? regards Arno Prakash -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Error Messages
Hi, thanks for that quick response, for the 1. what causes this message to appear??? 2. this comes up every time a user logs in to the domain / server i played arround with the log levels but i don´t found any information which group / object is missing net groupmap list returns following: Domain Guests (S-1-5-21-4226538298-1610114045-865933353-514) - domain_guests domain computers (S-1-5-21-4226538298-1610114045-865933353-515) - computers Enterprise Admins (S-1-5-21-4226538298-1610114045-865933353-519) - root Administrators (S-1-5-21-4226538298-1610114045-865933353-544) - root Guests (S-1-5-21-4226538298-1610114045-865933353-546) - domain_guests Account Operators (S-1-5-21-4226538298-1610114045-865933353-548) - account_operators Server Operators (S-1-5-21-4226538298-1610114045-865933353-549) - server_operators Print Operators (S-1-5-21-4226538298-1610114045-865933353-550) - print_operators Backup Operators (S-1-5-21-4226538298-1610114045-865933353-551) - backup_operators Replicator (S-1-5-21-4226538298-1610114045-865933353-552) - replicator Domain Admins (S-1-5-21-4226538298-1610114045-865933353-512) - root Users (S-1-5-21-4226538298-1610114045-865933353-1201) - users Domain Users (S-1-5-21-4226538298-1610114045-865933353-513) - users which looks to me ok regards arno Prakash Velayutham wrote: Hi, On Dec 30, 2004, at 9:28 AM, Arno Seidel wrote: Hi list, after searching google and getting lost in to much results, maybe someone can explain me the meaning of some error-messages: 1. [2004/12/30 14:10:03, 2] smbd/sesssetup.c:setup_new_vc_session(608) setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources. According to what I know, this is not an error. It is just information. 2. [2004/12/30 14:10:08, 0] passdb/pdb_ldap.c:ldapsam_search_one_group(2023) ldapsam_search_one_group: Problem during the LDAP search: LDAP error: (No such object) This means that the group you are intending to login as does not exist in your LDAP tree. When does this happen. Can you give some background? regards Arno Prakash -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Error Messages
Hi, 1. Are you able to login to the domain successfully? 2. Can you show some more of the log information from log.smbd or %m logs (%m is the name of the machine connecting). Do you see any error message similar to User Administrator in passdb, but getpwnam() fails! or check_sam_security: make_server_info_sam() failed with 'NT_STATUS_NO_SUCH_USER' Prakash On Thursday 30 December 2004 09:56, Arno Seidel wrote: Hi, thanks for that quick response, for the 1. what causes this message to appear??? 2. this comes up every time a user logs in to the domain / server i played arround with the log levels but i don´t found any information which group / object is missing net groupmap list returns following: Domain Guests (S-1-5-21-4226538298-1610114045-865933353-514) - domain_guests domain computers (S-1-5-21-4226538298-1610114045-865933353-515) - computers Enterprise Admins (S-1-5-21-4226538298-1610114045-865933353-519) - root Administrators (S-1-5-21-4226538298-1610114045-865933353-544) - root Guests (S-1-5-21-4226538298-1610114045-865933353-546) - domain_guests Account Operators (S-1-5-21-4226538298-1610114045-865933353-548) - account_operators Server Operators (S-1-5-21-4226538298-1610114045-865933353-549) - server_operators Print Operators (S-1-5-21-4226538298-1610114045-865933353-550) - print_operators Backup Operators (S-1-5-21-4226538298-1610114045-865933353-551) - backup_operators Replicator (S-1-5-21-4226538298-1610114045-865933353-552) - replicator Domain Admins (S-1-5-21-4226538298-1610114045-865933353-512) - root Users (S-1-5-21-4226538298-1610114045-865933353-1201) - users Domain Users (S-1-5-21-4226538298-1610114045-865933353-513) - users which looks to me ok regards arno Prakash Velayutham wrote: Hi, On Dec 30, 2004, at 9:28 AM, Arno Seidel wrote: Hi list, after searching google and getting lost in to much results, maybe someone can explain me the meaning of some error-messages: 1. [2004/12/30 14:10:03, 2] smbd/sesssetup.c:setup_new_vc_session(608) setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources. According to what I know, this is not an error. It is just information. 2. [2004/12/30 14:10:08, 0] passdb/pdb_ldap.c:ldapsam_search_one_group(2023) ldapsam_search_one_group: Problem during the LDAP search: LDAP error: (No such object) This means that the group you are intending to login as does not exist in your LDAP tree. When does this happen. Can you give some background? regards Arno Prakash -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error messages in log files with Samba 3.04
Hello list, I have recently upgraded to samba version 3.04 . Everything works well and a problem I had with one of my printers (which was the reason for upgrading) seems to be fixed. But now there is another issue. In the log directory there is a file called log.0.0.0.0 which in my opinion should not be there because obviosly there is no station with a 0.0.0.0 IP address. The error-messages: - getpeername failed. Error was Transport endpoint is not connected - Denied connection from (0.0.0.0) also appear in logs of existing users/stations. Does anyone know what is the cause of the errors and how to fix it ? Datei: log.0.0.0.0 [2004/05/12 07:10:26, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected [2004/05/12 07:10:26, 0] lib/access.c:check_access(328) [2004/05/12 07:10:26, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0) [2004/05/12 07:10:26, 1] smbd/process.c:process_smb(883) [2004/05/12 07:10:26, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 [2004/05/12 07:10:26, 0] lib/util_sock.c:write_socket_data(413) write_socket_data: write failure. Error = Connection reset by peer [2004/05/12 07:10:26, 0] lib/util_sock.c:write_socket(438) write_socket: Error writing 5 bytes to socket 22: ERRNO = Connection reset by peer [2004/05/12 07:10:26, 0] lib/util_sock.c:send_smb(630) Error writing 5 bytes to client. -1. (Connection reset by peer) [2004/05/12 14:37:13, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected [2004/05/12 14:37:13, 0] lib/access.c:check_access(328) [2004/05/12 14:37:13, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0) [2004/05/12 14:37:13, 1] smbd/process.c:process_smb(883) [2004/05/12 14:37:13, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 [2004/05/12 14:37:13, 0] lib/util_sock.c:write_socket_data(413) write_socket_data: write failure. Error = Connection reset by peer [2004/05/12 14:37:13, 0] lib/util_sock.c:write_socket(438) write_socket: Error writing 5 bytes to socket 5: ERRNO = Connection reset by peer [2004/05/12 14:37:13, 0] lib/util_sock.c:send_smb(630) Error writing 5 bytes to client. -1. (Connection reset by peer) [2004/05/13 07:20:05, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected [2004/05/13 07:20:05, 0] lib/access.c:check_access(328) [2004/05/13 07:20:05, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0) [2004/05/13 07:20:05, 1] smbd/process.c:process_smb(883) [2004/05/13 07:20:05, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 [2004/05/13 07:20:05, 0] lib/util_sock.c:write_socket_data(413) write_socket_data: write failure. Error = Connection reset by peer [2004/05/13 07:20:05, 0] lib/util_sock.c:write_socket(438) write_socket: Error writing 5 bytes to socket 22: ERRNO = Connection reset by peer [2004/05/13 07:20:05, 0] lib/util_sock.c:send_smb(630) Error writing 5 bytes to client. -1. (Connection reset by peer) best regards Andreas -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] error messages -- what does it mean?
Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 9 07:08:10 fileserver smbd[2025]: failed to decode PDU Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) Feb 9 07:08:10 fileserver smbd[2025]: process_request_pdu: failed to do schannel processing. I am using Samba 3.01 on Redhat 7.1. It's configured as a PDC. I think this error is new. This morning one user could not logon due to a bad filename in her Favorites folder in her roaming profile. Is that related to this error? -- Matthew Easton Sublunar Networks -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] error messages -- what does it mean?
On Tue, 2004-02-10 at 05:36, Matthew Easton wrote: Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 9 07:08:10 fileserver smbd[2025]: failed to decode PDU Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) Feb 9 07:08:10 fileserver smbd[2025]: process_request_pdu: failed to do schannel processing. I am using Samba 3.01 on Redhat 7.1. It's configured as a PDC. I think this error is new. This morning one user could not logon due to a bad filename in her Favorites folder in her roaming profile. Is that related to this error? No it is not. It is related to the way clients connect to our server for logons. When this fails, they re-negotiate the connection. I'll see about making the error message less scary. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Error Messages please help
Hi all! _1. Im running samba 3.0 with RH 9.0. I get error messages after successfull Domain-Logon to the Samba-Server. _ I have the following error messages : Jan 27 14:13:07 thinny smbd[8699]: [2004/01/27 14:13:07, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1357) Jan 27 14:13:07 thinny smbd[8699]: failed to decode PDU Jan 27 14:13:07 thinny smbd[8699]: [2004/01/27 14:13:07, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) Jan 27 14:13:07 thinny smbd[8699]: process_request_pdu: failed to do schannel processing. _2. My Server is acting as a PDC._ Is there any wrong in my global section, my be the socket options??Here is my global section: [global] #Allgemeine Einstellungen für einen PDC workgroup = Linux netbios name = thinny server string = Test announce as = Linux PDC announce version = 3.0 domain master = yes preferred master = yes domain logons = yes local master = yes time server = yes os level = 33 #Authentifizierung smb passwd file = /etc/samba/smbpasswd #Passwort DB syncron halten passwd program = /usr/bin/passwd %u pam password change = yes passwd chat = *password* %n\n *password* %n\n *successfully* \n passwd chat debug = yes unix password sync = yes #Logfiles log file = /var/log/samba/%m.log #log level = 1 passdb:2 auth:20 max log size = 1024 #Security security = user restrict anonymous = no encrypt passwords = yes admin users = @domainadm guest account = nobody interfaces = 10.17.1.1 hosts allow = 127.0.0.1 10.17.1. 10.17.2. 10.17.3. 10.17.4. 10.17.5. 10.17.6. 10.17.7. 127. password level = 0 #Users Home Drive logon drive = u: logon path = \\%N\%u\profiles #Logon Scripts #logon script = %u%.bat logon script = logon.bat #Performance socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Error messages
Hi all! Hi have the following error messages: Connections Denied: lib/util_sock.c:get_socket_addr(919) getpeername failed. Error was Der Socket ist nicht verbunden (0.0.0.0) : 4 Time(s) **Unmatched Entries** lib/access.c:check_access(328) : 4 Time(s) lib/util_sock.c:get_socket_addr(919) getpeername failed. Error was Der Socket ist nicht verbunden : 5 Time(s) lib/util_sock.c:get_socket_addr(919) getpeername failed. Error was Der Socket ist nicht verbunden Connection denied from 0.0.0.0 : 4 Time(s) lib/util_sock.c:read_socket_data(342) read_socket_data: recv failure for 1614. Error = Keine Route zum Zielrechner : 1 Time(s) lib/util_sock.c:read_socket_data(342) read_socket_data: recv failure for 4. Error = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt : 8 Time(s) lib/util_sock.c:read_socket_data(342) read_socket_data: recv failure for 4. Error = Keine Route zum Zielrechner : 8 Time(s) lib/util_sock.c:send_smb(585) Error writing 5 bytes to client. -1. (Die Verbindung wurde vom Kommunikationspartner zurückgesetzt) : 4 Time(s) lib/util_sock.c:write_socket(413) write_socket: Error writing 5 bytes to socket 16: ERRNO = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt : 1 Time(s) lib/util_sock.c:write_socket(413) write_socket: Error writing 5 bytes to socket 5: ERRNO = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt : 3 Time(s) lib/util_sock.c:write_socket_data(388) write_socket_data: write failure. Error = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt : 4 Time(s) What do they mean and have to do something to solve the problems ? mf PAUL -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Error messages
Hi, Can you help me.I have downloaded the latest version of samba 3.0.0. After having followed the instructions to configure compile etc I am getting the following error message when I run the command smbstatus. smbstatus Error trying to resolve symbol 'init_module' in /usr/local/samba/lib/charset/CP850.so: ld.so.1: smbstatus: fatal: /usr/local/samba/lib/charset/ ISO8859-15.so: open failed: No such file or directory Conversion from UCS-2LE to CP850 not supported Error trying to resolve symbol 'init_module' in /usr/local/samba/lib/charset/CP850.so: ld.so.1: smbstatus: fatal: /usr/local/samba/lib/charset/ ISO8859-15.so: open failed: No such file or directory Conversion from UTF8 to CP850 not supported Error trying to resolve symbol 'init_module' in /usr/local/samba/lib/charset/CP850.so: ld.so.1: smbstatus: fatal: /usr/local/samba/lib/charset/ ISO8859-15.so: open failed: No such file or directory Conversion from ASCII to CP850 not supported Error trying to resolve symbol 'init_module' in /usr/local/samba/lib/charset/CP850.so: ld.so.1: smbstatus: fatal: /usr/local/samba/lib/charset/ ISO8859-15.so: open failed: No such file or directory Conversion from CP850 to UCS-2LE not supported Unknown parameter encountered: printer driver file Ignoring unknown parameter printer driver file Processing section [Home] sessionid.tdb not initialised /usr/local/samba/var/locks/connections.tdb not initialised This is normal if an SMB client has never connected to your server. Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting ** Horizon Housing Group Ltd SLFHA Ltd Rother Homes Ltd Southern Horizon Housing Ltd Crystal Palace Housing Association Ltd *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any review, transmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error, please notify the sender or the Group's IS Operations Manager. Tel: (+44) 0208 768-2050 Horizon Housing Group Web Addresses: www.horizon-hg.org.uk www.slfha.org.uk www.rotherhomes.org.uk www.southernhorizon.org.uk www.sharedhorizons.org.uk --- www.st-martins.org.uk * -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Error messages about locking.tdb
Hi list, I am using Samba 2.2.3a-12 and it works fine, exept for error messages that fill up my log files. The messages are: smbd[1198]: [2003/02/12 22:53:53, 0] tdb/tdbutil.c:tdb_log(475) smbd[1198]: tdb(/var/run/samba/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) smbd[1198]: [2003/02/12 22:53:54, 0] tdb/tdbutil.c:tdb_log(475) smbd[1198]: tdb(/var/run/samba/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) The permission of /var/run/samba/locking.tdb is 600 root:root, the process trying to access it is an smbd running under a user account, so there seems to bee a configuration problem. I chnged the perms to 666 for a few seconds and now the log is quiet. Searching google did not show any solution. What's wrong here? System is Linux 2.4.18 SMP. Thanks for any help Heinrich -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - E-mail: mailto:[EMAIL PROTECTED] Phone : +49/421/218-4664 Fax :-3341 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Error Messages
Hello, We received the following errors when issuing the smbpasswd command in completing an install of the SAMBA 2.2.3a version onto an AIX 4.3.3 server. Can I get info on these error messages and whether they are critical to the install.? They did not seem to prevent us from finishing the install and once the server was recognized into the Microsoft domain, we were able to function as intended. But I want to understand these errors better. I appreciate any information you can provide. Thanks John Ortiz COTS Software Evaluation Management Team Lead National IRM Center - Bureau of Land Management 303 236-1832 voice 303 236-3327 fax - Forwarded by John Ortiz/NIRM/BLM/DOI on 05/03/02 10:28 AM - [EMAIL PROTECTED] l.blm.govTo: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] 04/29/02 03:24 Subject: Samba Error Messages PM root@tl0251:/usr/local/samba/bin # smbpasswd -jTESTLAB -rTL0014 cli_net_auth2: Error NT_STATUS_NO_TRUST_SAM_ACCOUNT cli_nt_setup_creds: auth2 challenge failed modify_trust_password: unable to setup the PDC credentials to machine TL0014. Error was : NT_STATUS_NO_TRUST_SAM_ACCOUNT. 2002/04/29 15:18:27 : change_trust_account_password: Failed to change password for domain TESTLAB. Unable to join domain TESTLAB. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
