search for: waynea

...y userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol pop3 { pop3_save_uidl = no pop3_uidl_format = %08Xu%08Xv } -------------- next part -------------- A non-text attachment was scrubbed... Name: waynea.vcf Type: text/x-vcard Size: 281 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20130614/e84fe9ba/attachment.vcf>

I have three samba 4.1.6 servers, all three are domain controllers. A, B , C, where A is has the FSMO role. I am getting the following error: [2015/02/02 11:49:42.359246, 0] ../source4/dsdb/samdb/ldb_modules/repl_meta_data.c:3664(replmd_op_possible_c onflict_callback) ../source4/dsdb/samdb/ldb_modules/repl_meta_data.c:3664: Unable to find replPropertyMetaData for conflicting record

Samba 4.0.0 I am running all of these commands from the PDC DC1. /etc/resolv.conf domain mydomain.com nameserver 127.0.0.1 smb.conf does have a dns forwarder = 192.168.1.2 samba-001 the actual host name, and also a PDC, in the same domain. I would like to have the alias my-server point to samba-001. I added a CNAME record: bin/samba-tool dns add 127.0.0.1 mydomain.com my-server CNAME

I am running Samba Version 4.1.6. I have a PDC and two BDC setup. I have a specific computer named eds, it is a Windows 7 Pro box, When I add it to the domain everything works normally and it works well. Domain users can login, and they have the proper permissions, but am seeing two problems. 1) Every once in a while I get: "The trust relationship between this workstation and the primary

I have been using Samba for quite a while now in my production environment, really since the very early releases of 4. There has been some pain here and there, but it has been an exciting and rewarding process. I have been noticing more and more changes in the environment, most minor but some more significant. A couple of examples. I did not use--use-rfc2307 when provisioning, it was not

I have had a problem for a couple of weeks now. I get very regular crashes on two of my three Domain Controllers. I just updated to 4.1.0 and I am still getting the same problem. I have added panic action = /bin/sleep 99999 to my config. Here is a back trace for the crash. (gdb) bt #0 0x003c3424 in __kernel_vsyscall () #1 0xb76fa363 in __waitpid_nocancel () at

I have 3 Samba 4 Domain Controllers and 1 Member server, been running in production for almost a year and very pleased with the results so far. I have winbind installed and working on all of my servers and I am also quite happy with that as well, except that the inconsistent uid and gid mapping is starting to cause some problems for me. I have done a fair bit of research and I think I would

I have Samba 4.0.9 installed on three Centos servers. On my primary DC I am getting faults and core dumps. Oct 2 06:10:37 dc1 smbd[1195]: [2013/10/02 06:10:37.083800, 0] ../lib/util/fault.c:72(fault_report) Oct 2 06:10:37 dc1 smbd[1195]: =============================================================== Oct 2 06:10:37 dc1 smbd[1195]: [2013/10/02 06:10:37.084493, 0]

> > I am running Samba Version 4.1.6. > > > > I have a PDC and two BDC setup. > > > > I have a specific computer named eds, it is a Windows 7 Pro box, When > > I add it to the domain everything works normally and it works well. > > Domain users can login, and they have the proper permissions, but am > > seeing two problems. > > > > 1)