similar to: idmap syntax transition from 3.0.20 to 3.0.25 ?

Hi Samba community, Last year we upgraded from version 3.0.10 to 3.0.20b and at the same time switch from NT-domain controller membership to AD membership. After this upgrade we began to experience that drives sometimes were not mapped. We saw this both on our Citrix servers and on our XP PCs. A couple of weeks back we then moved to 3.0.21b in the hope that this misbehaviour would

Dear list and Samba Team, It says in the Samba Howto, that it "should" be possible to trust a Windows 2000 domain, but it needs more testing. Have any of you made this work ? I ask because we implemented our Samba/LDAP-3 domain during the week-end and had to rool back since we couldn't get the user validation to a trusted Windows 2003 native domain to work. Samba team, If this

On 04/03/16 09:58, Volker Lendecke wrote: > On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: >> On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: >>> OK, here is the output: >> Can you try the attached (UNTESTED!) patch? >> >> Thanks, > Gna, should have at least compiled it.... > > New patch :-) > > Volker > Sorry

Hi again, For what it is worth, we found out that MS Outlook on Citrix now and then opens thousands(17-18000) of references(filehandles) to the same PAB(Personal Address Book) files and then give up these references again after a while !? This was what made Samba chooke. We will now remove all PAB access from Outlook. Sorry for wasting Samba mailing list bandwidth ;-) Kind

Dear Samba experts, Initially we set up winbind to the following: idmap uid = 10000-20000 thinking that 10000 uids were sufficient for the number of users we would get. We also have defined our UNIX users from 20001 onwards. However, now I can see that our latest windows(idmap uid) users has uid 19123 and this troubles me. Since I cannot just "extend" the

Dear list, Do any of you use the latest(3.0.4) as a Samba PDC(with OpenLDAP) on Linux ? If yes, have you encountered the following problem ? The setup is a PDC with an LDAP server running locally which is accessed directly and through nsswitch/PAM. A member server is providing shares to clients. When looking up domain users (wbinfo -u) from a member server(Solaris 8, OpenLDAP 2.1.25) there are

Hi List, Just a quick question for you: Does Samba 3.0.20 support the full_audit module? I've got the module operating on two boxes, one with Samba 3.0.25 and the other with 3.0.20, and only the former seems to interpret VFS directives, such as: full_audit:prefix = %u full_audit:failure = none full_audit:success = open write close On the 3.0.20 box, they seem to be ignored,

Dear all.. I moved my samba server to a new linux box (faster, bigger, etc..), and I moved from Mandrake 10.1 to 10.3 (mdk 2006).. I just copy my old configuration file to the new linux box. The new linux's distribution comes with samba 3.0.20... ( In my WinXP's clients I didn't change anything). Of course, it doesn't work.. My clients can't connect to the new samba server...

I am running Irix 6.5.12 and samba version 2.2.1 and am getting the following error message when trying to log onto a windows machine that has a samba mount mapped. System error 71 has occurred. No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. Any help would be appreciated as I am a newbie where samba

I've got a Samba PDC and a Samba domain member server. I successfully joined the domain, started winbind and run the wbinfo -p; wbinfo -t tests, both succeeded. But if I do a winbind -g I only get BUILDIN/group and if I do a wbinfo -u I get "Error looking up domain users". But ntlm_auth succeeds. So I'm a little confused. At this point this is a minor issue since

The following configuration has been working OK with Samba 3.0.1 Mandrake 9.0 PDC. Redhat 7.3 BDC. (both with ldapsam passdb backend). Solaris 8 Memberserver. After upgrade to 3.0.3pre2, exactly the same configuration - with exactly the same smb.conf - produces an error, when you try to add a user or group in the security settings of a file or directory through MS Explorer. The message text is

Dear list, I have just upgraded our main Samba server from version 2.2.8a to 3.0.6. It seems to be working fine except for 2 things: 1. when I use smbstatus(or swat/status) only some of the connections are listed and then smbstatus hangs forever(swat comes back after a while, but only with some of the connections) Have any of you experienced something similar ? How can I debug

On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: > On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: > > OK, here is the output: > > Can you try the attached (UNTESTED!) patch? > > Thanks, Gna, should have at least compiled it.... New patch :-) Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax:

Dear list, After having upgraded from Samba-2.2.8a to Samba-3.0.4 I have problems getting "short preserve case = Yes" to work properly for filenames having only capital letters when seen from NT-4.0 explorer. A mixture of lettercase filenames and all lowercase work fine. What I see is the following: UNIX: Windows-NT: --------

Dear list, We are experiencing users unexpectedly accessing each others files. It happens when they try to access files that are called the same and which is located in an equal file structure under their login drive. Two other conditions need to be fulfilled: one of the users needs to have the file locked and both users needs to be logged into the same Citrix server(windows-2000). For instance

We have a Samba PDC (Mandrake 9) a BDC (RH 7.3) and a Memberserver (Solaris 2.8). A configuration which is working OK in 3.0.1 seems to be broken in 3.0.3. Everything (except NTLM authentication) has been working fine. After installing 3.0.3 you cannot list domain users and the member server doesn't recoginize users as domain members. wbinfo gives the following results On PDC, BDC and

I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

Gerry, It looks like 3.0.25 breaks "stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict:

Hi, I'm currently using v3.0.24 in production and all works well. I'm testing 3.0.25 to see if I'm going to have any problems with it if I have to upgrade. I have a problem with the "force group" setting if it is set to a local Unix group. This same setting works fine in 3.0.24 but I'm denied access to the same share in 3.0.25. If I comment off the "force