similar to: Sometimes users can't connect to the samba shares

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

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

Folks, I do have a couple of problems I hope you could help to solve. I have searched the net, but had little success of finding documentation about samba 3.2 and AD. I do have Win server 2003 domain and AD in native mode. The new samba server should be a member server in the domain. The idea is to have same UIDs as the RIDs in the AD. The enviroment is as follows. Sernet packaged samba 3.2.3-37

Hello! I've integrated samba into an existing NT Domain managed by a windows 2003 server. Recently I'm have trouble to use the "groups" command get the group of domain users. It worked well for weeks (but perhaps after setting up an ldap-connection to the same server via the apache2 module auth_ldap), there are irregular connection-losses, so winbind seems not to be able to

Hello All, I don't know how, but I managed to get my no logon server found error to go away, but now I am experiencing another problem. When I run "net join ads -d 3" I get the following error message. I know it's authenticating, because if I enter an incorrect password it says "The username or password was not correct." So it's accessing the correct server, but

Hi everyone, We've been having intermittent problems connecting to Samba shares from Windows machines. I wrote a test program that tries to connect to the share and get a list of all of the files in it. It tries to do this every second. On some occasions this test program succeeds 14 times in a row before failing. It then fails once, and then succeeds 14 or so more times. It keeps repeating

Hi We have a problem with samba (winbind) when we enable idletimeout on the OpenLDAP servers. If it is set we sometimes get an error: mhansen@scenic32:~> smbclient -Umhansen //cups/p6 Password: session setup failed: NT_STATUS_IO_TIMEOUT The log entries (log.wb-DOMAIN)on the DOMAIN MEMBER server (cups in this case) are: [2006/11/20 14:24:07, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)

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

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

Hey, I've got an issue with winbindd seeming to periodically fail to resolve user/group names from an AD setup. I'm getting the following error, the error seems to occur when I try to access a the samba server OR a directory that uses AD dependent ACLs/permissions. The server will stall for around 30-40 seconds and then it all seems to work perfectly (though I haven't yet determined

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

Using "ldap password sync=yes" I can modify user password as admin through "net rpc user password" but if I try to modify it from the user (net rpc password myuser mypw -U myuser) or from windows (ctrl+alt+del). I get a timout error: [2006/03/16 21:52:40, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790) rpc_api_pipe: Remote machine alphacserver pipe \samr fnum 0x70e9returned

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

I have created a two way Interdomain Trust between a Samba 3.21 Domain and a Windows 2003 Server Domain. I am able to log into the Active Directory domain with my Samba users and I am able to access shares set up in the AD Domain. However, when I attempt to log into the samba domain with a user from the Windows 2003 domain, I get an error saying the username/password is not correct.  From the

Hello, We have a RHEL4 x64 running for 3 years, which is a samba member server integrated with a AD domain without any problems (we was using samba-3.0.10-1.4E.6). Last Saturday we performed an entire server update, applying all RHN available patches. Everything is running fine, except for winbind service which has a strange behavior: often we are receiving some errors at logs, and the

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

Hello, I'm having some trouble with the winbind process I'm getting a lot of error: [2005/07/04 14:14:48, 0] libsmb/clientgen.c:cli_send_smb(155) Error writing 494 bytes to client. -1 (Broken pipe) [2005/07/04 14:14:48, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435) cli_pipe: return critical error. Error was Write error: Broken pipe [2005/07/04 14:14:49, 0]

Hi all, I have 2 Linux machines running winbind attached to a Windows 2003 server in AD mode to resolve users and groups via nss (nscd is disabled for passwd and group info). In an intermittent way winbind stops resolving group names, for instance the 'id' command returns just the GID and no name for the primary user group and executables trying to resolve members of groups cannot