Dear List Members We are currently using samba-3.0.10-1.4E.2-x86_64 on RedHat AS 4. And it seems that we are suffering of the same problems reported here: http://lists.samba.org/archive/samba/2005-April/104335.html problems with the service pack 1 for windows 2003 [2005/04/25 02:06:33, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(993) api_pipe_bind_req: unknown auth type 1 requested. I was wondering if samba-3.0.10-1.4E.6-x86_64, which is now available through the RedHat Network channel, includes the necessary patches or not. Is this numbering schema identical to the one used by the samba- team? I know that RedHat backports but is RedHat 3.0.10 really samba- team 3.0.10? Searching through samba.org site I found the binaries provided by http://enterprisesamba.com/. Should we leave the RedHat Channel and use samba3-3.0.23-26.x86_64.rpm instead? Any comments on the quality of these packages? We don't really want to compile samba ourselves anymore. Kind regards, Marc
On Thu, Jul 13, 2006 at 11:44:05AM +0200, Marc Petitmermet wrote:> I was wondering if samba-3.0.10-1.4E.6-x86_64, which is now available > through the RedHat Network channel, includes the necessary patches or > not.This is something which you should ask RedHat. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20060713/be8d5919/attachment.bin
Maybe Matching Threads
- Samba 3.0.10-1.4E and RedHat Enterprise 4.
- Red Hat Enterprise and samba
- samba in centos 4.4: samba-3.0.10-1.4E.9 versus the latest from sernet samba3-3.0.23c-30
- ADS joined, can't manage shares from MMC
- "Attempt to bind using schannel without successful serverauth2" in 3.0.20 logs