I'm doing some testing with Win7 RC1 and I'm having an identical problem with two CentOS servers (5.2 and 5.3) both running Samba 3.0.33 where I cannot authenticate. Both servers are authenticating with Winbind to an AD DC. I have a third CentOS 5.2 server with Samba 3.0.33 shares that does not use Winbind which has no problems.
This pops up in smbd.log: (.200 is wireless and .184 is my wired IP.) [2009/06/25 09:06:13, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client 10.1.13.200. Error Connection reset by peer [2009/06/25 09:06:14, 0] lib/util_sock.c:send_smb(761) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/06/25 09:19:03, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client 10.1.13.200. Error Connection reset by peer [2009/06/25 09:19:03, 0] lib/util_sock.c:send_smb(761) Error writing 4 bytes to client. -1. (Connection reset by peer) [2009/06/25 09:21:41, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client 10.1.13.184. Error = Connection reset by peer The Win2K DC logs the following (3221225578 = bad password?): The logon to account: cgarst by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: \\RAVAGE failed. The error code was: 3221225578 Perhaps Samba/Winbind are not passing the authentication packages to the DC correctly? Any suggestions? Thanks. -Corey Garst -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
