[Samba] Planning to upgrade to samba-3.0.33-3.37.el5.x86_64 version from samba version 3.0.25b-1.el5_1.4 ------------ queries needed to be answered.

Marc Muehlfeld samba at marc-muehlfeld.de
Mon Jun 24 22:41:17 MDT 2013


Hello Prasanjit,

Am 18.06.2013 23:45, schrieb Shome, Prasanjit (TCS):
> Hi All,
>          Need help regarding the samba version samba-3.0.33-3.37.el5.x86_64
>
>
> 1)      In the samba version (samba-3.0.33-3.37.el5.x86_64) that we are planning to use , if we put multiple password server names like the one shown below
>
>          workgroup = EUROPE         --------- we do have a domain named as EUROPE [ as per windows team ]
>          password server = EUREDD-HUB10 EUREDD-HUB09 *
>          security = domain
>
> a)      Is this the right format ?
> b)      Is there any provisioning of any load balancing of user requests for authentication if we use multiple password servers ?
>
> 2)      what are the scenarios or conditions in which samba will hop to another password server mentioned in the list ?
>
> 3)      can you let us know the working functionality how samba client tries to connected to DC and eventually to the samba Linux (in our environment) server ?
>
> 4)      In our environment, we have seen recurring connectivity issues over WAN (primarily) and authentication failure issues (shown below) while using samba version 3.0.25b-1.el5_1.4. Can you please let us know if there is any bug fixes made against those concerned issues if we upgrade to samba-3.0.33-3.37.el5.x86_64.
>
>
> Jun  5 10:34:18 afsdl1p smbd[800]:   EUREDD-HUB09 rejected the initial session setup (Call timed out: server did not respond after 20000 milliseconds)
> Jun  5 10:35:19 afsdl1p smbd[7396]:   EUREDD-HUB09 rejected the initial session setup (Call timed out: server did not respond after 20000 milliseconds)
> Jun  5 10:35:19 afsdl1p smbd[7407]:   tdb_chainlock_with_timeout_internal: alarm (10) timed out for key EUREDD-HUB09 in tdb /etc/samba/secrets.tdb
> Jun  5 10:35:39 afsdl1p smbd[7407]:   EUREDD-HUB09 rejected the initial session setup (Call timed out: server did not respond after 20000 milliseconds)
> Jun  5 10:36:10 afsdl1p smbd[11177]:   EUREDD-HUB09 rejected the initial session setup (Call timed out: server did not respond after 20000 milliseconds)
> Jun  5 10:36:10 afsdl1p smbd[11991]:   tdb_chainlock_with_timeout_internal: alarm (10) timed out for key EUREDD-HUB09 in tdb /etc/samba/secrets.tdb
> Jun  5 10:36:27 afsdl1p smbd[12006]:   tdb_chainlock_with_timeout_internal: alarm (10) timed out for key EUREDD-HUB09 in tdb /etc/samba/secrets.tdb
> Jun  5 10:36:41 afsdl1p smbd[15252]:   tdb_chainlock_with_timeout_internal: alarm (10) timed out for key EUREDD-HUB09 in tdb /etc/samba/secrets.tdb
>
>
>    eurhil-app02 (155.248.158.28) connect to service HIL_MFG initially as user afshil (uid=340, gid=340) (pid 18258)
>    eurhil-app02 (155.248.158.28) closed connection to service HIL_MFG
>    read_data: read failure for 4 bytes to client 155.248.158.28. Error = Connection reset by peer
>    eurhil-app02 (155.248.158.28) connect to service HIL_MFG initially as user afshil (uid=340, gid=340) (pid 25382)
>    eurhil-app02 (155.248.158.28) closed connection to service HIL_MFG
>    read_data: read failure for 4 bytes to client 155.248.158.28. Error = Connection reset by peer
>    eurhil-app02 (155.248.158.28) connect to service HIL_MFG initially as user afshil (uid=340, gid=340) (pid 29851)
>    eurhil-app02 (155.248.158.28) closed connection to service HIL_MFG
>    read_data: read failure for 4 bytes to client 155.248.158.28. Error = Connection reset by peer
>    eurhil-app02 (155.248.158.28) connect to service HIL_MFG initially as user afshil (uid=340, gid=340) (pid 3793)
>    eurhil-app02 (155.248.158.28) closed connection to service HIL_MFG
>    read_data: read failure for 4 bytes to client 155.248.158.28. Error = Connection reset by peer


I know, that this is not answering your questions, but: Is there a 
reason, why you need to update from a 10 times old and unsupported 
version to a 9 times old and unsupported version? :-) The 3.0 tree is 
discontinued since August 2009.

Maybe many of your problems will disappear with a newer version, that 
contains a lot of new functions, fixes, better performance, etc.

Sernet provides RPMs of all supported versions, if you don't want to 
compile.

Regards,
Marc


More information about the samba mailing list