similar to: Win(yuck)NT

In migrating to Samba on FreeBSD from WinNT, I've run into this hitch. Let us say I have 9 users named User1, User2, User3, ? User9 User1 is a member of group wheel User2 & User3 have the administrative task (add/change/delete) of managing the content of the directory Dirc1 and all subordinate objects (files and directories). Dirc1 is the directory /usr/Shared/Dirc1. Only

I have experienced a couple of (minor) problems with Samba Thought I would report these and ask if they are known problems. 1. Problem with "!" in username map file 2. Samba tools e.g. smbstatus, testparm not accounting for "config file" parameter 1. There appears to be a problem with a minor part of username map file interpretation. When I put an exclamation mark

Ok, you are completely right. Here are the real numbers with changed user names: drwx------ 43 DOM\user1        DOM\domain-user  4096 Jan 10 08:00 user1 drwx------   5 DOM\user2        DOM\domain-user  4096 Jan 11 08:13 user2 drwx------ 92 DOM\user3        DOM\domain-user   4096 Jan 16 08:39 user3 drwx------   3        133265        DOM\domain-user   4096 Sep  7 2015 user4 drwx------   7       

Am 16.01.2018 um 17:26 schrieb Rowland Penny via samba: > On Tue, 16 Jan 2018 16:54:17 +0100 > Andreas Hauffe via samba <samba at lists.samba.org> wrote: > >> Ok, you are completely right. Here are the real numbers with changed >> user names: >> >> drwx------ 43 DOM\user1        DOM\domain-user  4096 Jan 10 08:00 >> user1 drwx------   5 DOM\user2       

Hi, no, that's my fault. I changed the UIDs and user names in my "ls -l" to unpersonalized/example data for my mail and didn't think about putting these values into the range. A better unpersonalized data example would look like: ---------- drwx------ 43 DOM\user1        DOM\group  4096 Jan 10 08:00 user1 drwx------   5 DOM\user2        DOM\group  4096 Jan 11 08:13 user2

Problem number one: ------------------- I'm running a few-hours-old CVS version of Samba 3.0 with LDAP as the authentication backend, and I'm having some problems trying to set up the LDAP accounts using "smbpasswd". I build the structure of the LDAP database by importing a couple of LDIF's, and then I import the following user account to create an administrative account

Hello. Is this normal. Or does it mean there is a problem ? ------------------------- stop now Beginning asterisk shutdown.... Executing last minute cleanups == Destroying any remaining musiconhold processes Yuck! Error in buffer handling...: Connection reset by peer Yuck! Error in buffer handling...: Broken pipe Yuck! Error in buffer handling...: Broken pipe Asterisk cleanly ending (0).

[root@red docs]# net rpc vampire -S NTPDC -d 3 [2004/08/17 14:09:29, 3] param/loadparm.c:lp_load(3911) lp_load: refreshing parameters [2004/08/17 14:09:29, 3] param/loadparm.c:init_globals(1324) Initialising global parameters [2004/08/17 14:09:29, 3] param/params.c:pm_process(566) params.c:pm_process() - Processing configuration file "/usr/lib/smb.conf" [2004/08/17 14:09:29,

Hi, The group that is mapped to rid=512 cannot be used in "valid users", the users cannot map the share (error 5). Is this normal? Should I file a bug? Version 4.1.6-Ubuntu server role = classic primary domain controller smb.conf: valid users = +smbadmin command: net groupmap add ntgroup="Domain Admins" unixgroup=smbadmin rid=512 type=d As soon as I remove the group

Morning, Well I ordered a Windows Server 2008 Standard for a need around here and after just spending an hour with Dell support (nice fellow, not his fault) I find that now the 2008 Server is too *new* for the Samba NT4 PDC model. I got this box joined fine with my domain, but any time I try to log into it over RDP, and the new box authenticates with samba (and samba talks to OpenLDAP) the box

After reading through the documentation, I realized that as a part of the migration process from Samba-2.2.X to Samba-3.0.0 I needed to convert everyone in my smbadmin group (previously domain admin group = @smbadmin) to the "Domain Admins" group w/rid=512. So, I issued the following command: [root@localhost profile]# net groupmap modify ntgroup="Domain Admins"

I have an [apps] share that was intended to be read-only (to keep viruses away) however some Windows programs require rw access to specific files. I don't want to open-up everything on the share to rw, only those specific files/directories that need 'w' access. Here's the dilemma: In order for users to be able to change a file, the file and directory it's in need to have rw

Hi, I'm currently running CVS-HEAD 2005-09-03 I do plan to upgrade to the newest version, but need to do some testing with it first. In the mean time... does anyone know what these messages below are about? I've never seen it before, but when it happened it locked Asterisk up pretty good. Feb 10 10:16:51 DEBUG[14917] chan_zap.c: Echo cancellation already on Feb 10 10:16:57

Hi! I have a problem with roaming profiles which I don't understand. I can login and logout from XP with a samba PDC with ldapsam flawlessly, but for some reasons when the profile does not belong to the user itself windows tells me upon logout that it cannot copy back some files to the server. Weird, because the directory where the profile resides is readable and writable by the user,

when trying to put a samba3 server into a domain (samba3 pdc) I always get the following error messages: [root@file samba]# net join -d 2 -U smbadmin RHEL -S server1.example.com [2004/09/30 23:36:35, 2] lib/interface.c:add_interface(79) added interface ip=192.168.0.150 bcast=192.168.0.255 nmask=255.255.255.0 smbadmin's password: [2004/09/30 23:36:37, 1] libads/ldap.c:ads_connect(251)

I had our production systems running on rc23, however we ran into problems when the server was under heavy load. Eventually, the server would begin to freeze all imap connection after authentication (according to the logs). A user would connect, authentication would succeed, and then the connection would sit until timing out. No error logs were produced. Upgrading to rc24 did not

I am using AD DC. I already have a domain Samba3 + Openladp, I'm creating this new domain Samba4, but I want to import all users who have already registered in my base Openldap. If it was the same demesne I would use the migration tool, but it's a different domain. -- View this message in context:

Hi! I'm experiencing strange performance problems after upgrading to samba 3.2.8 from 3.0.30. For all users except smbadmin (who has administrative rights), read performance is _very_ bad. Looking at the read-requests using filemon and wireshark, I found out that for those users, every read is handled transparently (unbuffered) over the net. (I.e. a 2 byte read-request of the application

Sorry if this is a dup. I sent right before I subscribed to the list, so I'm not sure if it made it. I have just taken over a redhat system with Samba 3.0.0 configured with security = user, and domain logins enabled. I've included the smb.conf at the end of this message. I would like to upgrade to 3.0.10 for a numbers of reasons, one being security and one being that password changes

OK, I had this working a few days ago, but have evidently changed something that I cannot locate. Someone hit me with their 2x4. Samba 3.0.22, Fedora Core 4, ldapsam (OpenLDAP 2.3.24). smbd will not start, with the "ERROR: failed to setup guest info" error (I have "guest account = guest", which is a valid user with correct info in LDAP): ldap_connect_system: Binding to ldap