similar to: Winbindd and idletimeout on the LDAP server

While I was updating our ssh-servers, I rewrote my old patch that adds idletimeout (just like in old ssh1) parameter to openssh. Since reapplying the patch for all new versions of openssh is not fun at all, I would like to have it included in the official openssh, if you consider the patch worthy. Unlike ClientAlive, idletimeout works for both protocol versions. It also works together with

Here is my third attempt at the idletimeout patch. I tried to address the points which Marcus Friedl brought up. It is actually bigger than the previous patches, but not as intrusive. It is big because it moves some stuff from serverloop.c to packet.c. - I moved all the logic to packet.c. This means that I also had to move the actual select() call, which used to be in serverloop.c to packet.c.

Doing a search in the list archives, I see that in 2001/2002 there was a patch made available for IdleTimeout keyword, for example: http://marc.info/?l=openssh-unix-dev&m=99838019319356&w=2 Looks like that patch did not make it in the following versions of OpenSSH - is there a reason why - any chance of the patch getting back in? I do know about ClientInterval, but I think I need

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i I have a problem with a samba-3.0.21a (as a PDC), when I use rpcclient to set the driver for a printer. I receive the following error (log level 12 for relevant parts rpc*, printerdrivers,tdb attached): rpc_api_pipe: Remote machine pdc pipe \spoolss fnum 0x76dereturned critical error. Error was Call returned zero bytes (EOF) prs_mem_get: reading

We are in the process of upgading our windows 2003 pdc's to windows 2008Rr2. No problem there, but our samba/winbind clients are beginning to show some strange behaviour. In the beginning we saw a lot of messages appear in the logfiles. Example : -------------- pr 1 14:07:36 srvxxx winbindd[5148]: rpc_api_pipe: Remote machine pdc.company.net pipe \NETLOGON fnum 0x4003returned critical

Hi We have an all SAMBA Domain (all samba-3.0.23d) running with two OpenLDAP servers (2.3.27). We experience quite a few NT_STATUS_IO_TIMEOUTs when using smbclient. Windows clients just experience delays (up to several minutes). I've done some debugging: On the client i issue: smbclient -Umhansen //lfs1/mhansen lfs1 is a domain member server. On lfs1 (log level 10) i get the following in

Hello.. I would like to know if there is a keyword in OpenSSH analogous to IdleTimeout for SSH1. Is there the ability to configure an idle timeout in OpenSSH? Thanks in advance for your response Amba Giri Symbol Technologies, San Jose P: 408-528-2721 E:agiri at sj.symbol.com Symbol. The Enterprise Mobility Company.

smbd version 3.0.25b-0.4E.5 Our server was functioning very well for several months. Our SAN crapped out and the LUN the server was using was gone. Everything is back up except SAMBA is acting crazy. I am looking at the logs and I am getting /var/log/samba/winbindd.log winbindd: Exceeding 200 client connections, no idle connection found and ads_krb5_mk_req: krb5_get_credentials failed for

Samba occasionally fails with the following. I have seen many questions regarding this but no answers unfortunately. I am wondering what the setting is where I can increase this time out value of 10000 milliseconds in case that specific request is just slow. This is called many times a day and only just occasionally fails. I have looked through the entire manual for smb.conf and can't find a

I have compiled Samba 3.0.22 on Solaris 10 (sparc.) It has been configured as a PDC with a domain of, say, "SAMBADOMAIN." It has some predefined group mappings for the Administrators and "Domain Admins" group. These mappings were dropped in later versions of Samba. (I have been working with 3.0.24 as well. Unfortunately it doesn't seem to play nice with

http://bugzilla.mindrot.org/show_bug.cgi?id=1338 Summary: Idletimeout for both client and server Product: Portable OpenSSH Version: 4.6p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy: wmertens at

Hi! I've shared a CUPS Printer via Samba, Samba is connected to a Win2003 SP1 Domain to authenticate users. Most of the time all works nice, but sometimes there are errors. For example it seems that a WinXP client can't deliver the print-jobs to samba/cups anymore. The jobs just stay in die windows Printer queue. log.smdb: [2007/04/03 11:13:34, 2]

I am running a very mixed network, Linux, win nt4 servers OS X, Linux, Win 98SE, 2k, & XP clients just added a new ubuntu server running samba 3.0.22. (new server a replacement for an old NT4 server) NT 4 is PDC Everything was mostly fine for about a month, then started getting errors logging into shares. At first I could fix this by restarting winbind, but then came times when I was

Hello, Occasionally when I perform "net rpc group members (group a)," I get a timeout. When I do "net rpc group members (group b)," I always get a timeout. I get the following error: [2007/01/05 16:36:18, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790) rpc_api_pipe: Remote machine 127.0.0.1 pipe \samr fnum 0x72cdreturned critical error. Error was Call timed out: server did not

Hello, I have been using samba to authenticate my squid users to Active Directory. Because of the amount of users, I would like to set up my ACL's based on groups, rather than individual user accounts. I have successfully joined my samba box to our windows domain (2k). For some reason I had to enter the domain controller name instead of the domain name when doing so. I am now having issues

HI, After a quite long period wehere samba was wroking well, sudenly, with an apparently good reason started do not work. This mean the user are not able to connect to server, to samba shares. this is something i could find in logs. I google it for something like: [2009/08/21 13:59:16, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790) rpc_api_pipe: Remote machine DC01.mydomain pipe \NETLOGON fnum

Hi all we have samba 3.0.21c with OpenLDAP backend as PDC and also 4 BDC's Suddenly on PDC we are getting these error messages in /var/log/messages I am unable to register any system to the domain. niether able to logon to the domain. ########################################################################################## Feb 15 11:14:32 msdpl smbd[18212]: [2007/02/15 11:14:32, 0]

This is my first step into the world of samba and I was wondering if the members of the group wouldn't mind casting a quick eye on my setup. Essentially we just want Samba integrated with AD so we can access the Unix file systems. Any comment will be gratefully received...! Cheers, Kristian Everything seems to work, although we do get these errors: [2008/08/08 11:41:13, 1]

Been working with Samba back to 1.9 or so, but this is the first time I've tried to set it up as a domain member server. I followed (I think) the instructions on how to do this in TOSHARG (which are about as disjointed as the book, which I took back), but I continue to be unable to get the box, running winbind, to reliably authenticate users off the PDC, which is running NT4 (and I'm not

Hi All, I've been having a problem recently with LDAP queries for group names in winbind. I'm fairly certain the problem is to do with the fact that I'm using a round robin dns name for the password server. When samba starts it attaches itself to what I presume is the first server that returns from the dns lookup. When that server is taken down for maintenance it causes winbind to