[Samba] Windows 7 RC1 Build 7100 Cannot Connect to Samba Sharesw/Winbind

[Matthias Grimm]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 25.06.2009 17:06, schrieb Corey Garst:

I'm using sernet's centos-packages from tested on all of my samba
servers and from experimental on my ctdb cluster. W7 RC1 connects fine
as domain member to the cluster, which is AD-backed.
Sernet's packages and repo could be found here:

ftp://ftp.sernet.de/pub/samba/

Matthias

> I'm using the CentOS package now, what's the recommended upgrade path? I notice that samba.org links me to some samba5 packages that don't upgrade the CentOS. packages. Can I just install samba5 over samba? Are there any alternate packages available that would upgrade CentOS samba?
> 
> http://enterprisesamba.com/index.php?id=123
> 
> -Corey
> 
> 
> -----Original Message-----
> From: Mössler, Michael [mailto:Michael.Moessler at uhb-consulting.de] 
> Sent: Thursday, June 25, 2009 10:42 AM
> To: Corey Garst
> Subject: AW: [Samba] Windows 7 RC1 Build 7100 Cannot Connect to Samba Sharesw/Winbind
> 
> Hi Corey,
> 
> Try using an actual  newer Version of Samba Version 3.2.7-11.2.1-2080-SUSE-CODE11
> Works well now for us, ist the same Issue like Vista and W2k8 Server has.
> 
> 
> 
> _________________________
> Michael Mössler
> Beratung
> uhb consulting AG
> Chiemseering 1
> 84427 St. Wolfgang
> Tel.: 08085/939   131
> Fax: 08085/939 - 2131 
> 
> -----Ursprüngliche Nachricht-----
> Von: samba-bounces+michael.moessler=uhb-consulting.de at lists.samba.org [mailto:samba-bounces+michael.moessler=uhb-consulting.de at lists.samba.org] Im Auftrag von Corey Garst
> Gesendet: Donnerstag, 25. Juni 2009 15:53
> An: samba at lists.samba.org
> Betreff: [Samba] Windows 7 RC1 Build 7100 Cannot Connect to Samba Sharesw/Winbind
> 
> 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
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkpDrsgACgkQf3LySRiTg2xovACdGRs5mybMIhyNe8ojElIx2LDd
ILsAn2ow+YChUOXHJa+CNAmkhpofue+K
=ALex
-----END PGP SIGNATURE-----