similar to: Replication problems in Samba 4.1.18

Hello Marc, > What schema version does your AD have? > http://www.itguydiaries.net/2012/09/how-to-find-current-active- > directory.html > > Samba is shipped with AD schema 47 (MS Windows Server 2008 R2). Maybe > you already run a newer schema version or had done schema enhancements, > that are currently not supported by Samba. AD scheme version is 47. However, a few years

"schema enhancements [...] are currently not supported by Samba." Does this applies only when connecting a Samba DC on MS AD or is the replication broken also when we enhance schema on Samba-only-domain? Cheers, mathias @Marc, as you can imagine I'm not too aware about schema modification and Samba replication restriction, but it seems this Office Communication Server schema

Hi, I installed and configured Samba 3.0.23c as a domain member. I am running winbindd on Solaris 8 Sparc. I am seeing a strange behavior after the configuration. If I issue a "wbinfo -g" I see all the NT groups. Likewise, if I issue a "wbinfo -u" I see all the NT users. Continuing on with a "getent passwd" shows me the combined Unix and NT accounts, but

Hello all, I have a pretty large DC and am using winbind for our linux workstations and im having a preculiar issue. Not all accounts but some...including mine are recieving the pam error to change password. example... ... WARNING: Your password has expired. You must change your password now and login again! Changing password for user msellers. Changing password for msellers (current) NT

Dear Samba friends, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The upgrade went quite smoothly in general, but I encountered some difficulties with the printer

Dear Samba friends, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The upgrade went quite smoothly in general, but I encountered some difficulties with the printer

Hello, i hope u guys can help me. This is the first time I write to the list. Sorry about my english... i got a solaris 10 machine and installed "samba 3.0.2.3c" with "openldap 2.3.2.1" , "openssl 0.9.8" and "gcc 3.4.6". i configured kerberos and all the other things. all good. i added the samba-server (solaris10) to a active directory domain. with

Dear R helpers, I have been using the loadings function from the multiv library and I get the typical output (see below). When I try to export these results to a file using a write.table() I get the following error message "Error in as.data.frame.default(x[[i]], optional = TRUE) : can't coerce loadings into a data.frame" Any idea why write.table is doing that and any

Hello, I'm having problems with group consistencies between my samba server and a trusted domain. I'm running 3.0.23b with my samba server a member of an NT domain, which in turn trusts another domain (AD mixed mode). The AD admin added a user into a group, but my samba server sees the user as being added to a different group. Any ideas? Regards, Franz

Hi there Just a couple of questions to help me understand. When I upgrade from 3.0.22 to 3.0.23c the access restrictions on my shares on the member server no longer work. I read in the Changes file "Since Samba 3.0.8, it has been recommended that all domain accounts listed in smb.conf on a member server be fully qualified with the...." So far so good I know what I have to do still I

Hello, In the documentation it's writen (https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO) We do not recommend using the Domain Controller as a file Server What are the best practice in a environement with only 10 pc If you have just one physical computer (vm,lxc,..) Thanks -- probeSys - spécialiste GNU/Linux site web : http://www.probesys.com

Hello, Using samba 3.0.23c on Debian 3.1 (package version 3.0.23c-1~bpo.1 from sarge-backports) or version 3.0.14a (package version 3.0.14a-3sarge2 from sarge), I experience the following problem on a file server on a Windows 2003 domain with Active Directory. Some test user can access group shares of groups he is not in, or cannot access group shares of groups he is in. The output of the

I've got a client - a cheap client - and they want to add a new file server (samba sharing) to their network. They have one samba server already acting as the domain controller (PDC) and file server (and DHCP server). The wiring is a nightmare, and everything is daisy chained through 3 different non- programmable switches. They have no more open ports on any of the switches. Further, the

Hi all! Im using samba 3.0.23c from debian backports and I finding some problems, this host has worked flawlessly since a a few months ago. But now stopped to work properly. My versions are: ii winbind 3.0.23c-1~bpo.1 service to resolve user and group information from Windows N ii samba 3.0.23c-1~bpo.1 a LanManager-like file and printer server for

hi, i just do some tests with a fresh compiled samba 3.0.23a. trying to authenticate against PAM with pam_winbind gives: Aug 1 09:59:21 humevo36 pam_winbind[27853]: pam_winbind: pam_sm_authenticate (flags: 0x0000) Aug 1 09:59:23 humevo36 pam_winbind[27853]: Verify user `gasch' Aug 1 09:59:23 humevo36 pam_winbind[27853]: enabling cached login flag Aug 1 09:59:23 humevo36

Are you running with DHCP IP adress? ( not adviced ) i see, .. >dns forwarder = 127.0.1.1 run : hostname -i hostname -I if you see anything with 127.0.x.x Then your setup is not correct and can have problems. ( for example with authentication. ) please make sure your /etc/hosts file does not contain 127.0.1.1 of sorts. like : 127.0.0.1 localhost localhost.localdomain 192.168.0.1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Here's a new adage for you: "Don't let the crazy hacks take over". -- Tridge ============================================================== Release Announcements

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Here's a new adage for you: "Don't let the crazy hacks take over". -- Tridge ============================================================== Release Announcements

Hi List, I used samba-4.1.18 as domain controller and tried to use romaing profile. I got memory leak when every account with profile path setting logout. Every account with profile path setting eat almost 10mB memory so my samba machine crash if there are many hundred account with profile setting in domain. Any option in smb.conf or operation can help ? This is my reproduce setps: 1. create

I have been at my wits end now since Sunday trying to debug an issue that occurred when I tried to update from sernet-samba-4.1.18 to sernet-samba-4.2.2 on my small network. I have one administrator account and two user accounts which I will call account1 and account2. Before I updated I was able to login into any of 3 Windows 7 Professional boxes and 5 linux boxes running CentOS 6.6 using