similar to: IDMAP/GID2SID/1004 couldn't be found

I upgrade a samba 3.2.14 to samba 3.6.0 radius server for 802.1x. I discover that ntlm_auth fails for machines accounts with error: No logon workstation trust account Put winbind in debug with winbindd -F -i -d 10 give: accepted socket 24 process_request: request fn INTERFACE_VERSION [20000]: request interface version winbind_client_response_written[20000:INTERFACE_VERSION]: delivered response

Hi , I'm trying to migrate an old server with ubuntu 9.10 ,samba3 +ldap to a new server ubunut 14.04. I could follow the steps of https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_domain_to_a_Samba_AD_domain_%28classic_upgrade%29 but when running samba-domain tool classicupgrade --dbdir = / util / tdb --use-xattrs = yes --realm = gruporesasco.local --dns-backend = BIND9_DLZ

Hi! I'm apologize for my poor English, but have a question. This question is a shorter than one i posted not so long ago (https://lists.samba.org/archive/samba/2013-September/175649.html) and received no answer for a while. In this question i took a log from the different server, but this is no matter: the problem persists on all of my servers. So, my OS is FreeBSD 9.0, my Samba is 3.6.18

Greetings! I have a samba 3.6.18 acts as a domain member. I'm using a samba nss and creating local groups for a domain users. Here part of my nsswitch.conf: group: files winbind passwd: files winbind The problem is that the tdb unix GID mappings returns different ID from time to time for the same SIDs. Suppose we have a local group "samba_svn1", created with "NET SAM

Hi Mathias, greping in the output of "net cache list" shows: Key: IDMAP/GID2SID/20513 Timeout: Mon May 9 07:29:11 2016 Value: S-1-5-21-1891182457-2156988848-2018633412-513 Key: IDMAP/GID2SID/100 Timeout: Mon May 9 07:29:32 2016 Value: S-1-5-21-1891182457-2156988848-2018633412-513 Key: IDMAP/SID2XID/S-1-5-21-1891182457-2156988848-2018633412-513 Timeout: Mon May 9

On 02/05/16 15:08, Stefan Schäfer wrote: > Hi Mathias, > > greping in the output of "net cache list" shows: > > Key: IDMAP/GID2SID/20513 Timeout: Mon May 9 07:29:11 > 2016 Value: S-1-5-21-1891182457-2156988848-2018633412-513 > Key: IDMAP/GID2SID/100 Timeout: Mon May 9 07:29:32 2016 Value: > S-1-5-21-1891182457-2156988848-2018633412-513 >

Hi Quick question about something I find surprising: In tdb mode : net cache list -s /etc/samba/smb.conf |grep '\-513' Key: IDMAP/GID2SID/100?? ? Timeout: Tue Apr? 9 14:34:48 2024 Value: S-1-5-21-1040823229-2152490729-3717368692-513 id of group "domain users" is?100 But id 100 use by "users" system group: getent group|grep users users:x:100: Is this something

Hi all The symptom is: > C:\Windows\system32>net USE z: \\10.10.23.219\share /USER:SMBUSER > [password] > > System error 1326 has occurred. > My situation I am using VirtualBox. Windows 7 Home is the host. Fedora 13 is the guest. My goal is to cause the Fedora guest to expose an smb share to the Win 7 host and have the Win 7 host mount the share as a drive. My procedure:

When I run the following "net lookup sid" command, I get: # net lookup sid S-1-5-21-1908027396-2059629336-315576832-12220 S-1-5-21-1908027396-2059629336-315576832-12220 1 (User) \fhess This is wrong in that "\fhess" should be "NIST\fhess". The other direction works fine: # net lookup name "NIST\fhess" S-1-5-21-1908027396-2059629336-315576832-12220 1

Hi ! I'm running a samba domain controler under rhel 5. It's version 3.0.33-3.7.el5. I've also installed a ldap server to store users and groups and so on. When I try a pdbedit -v david, I get the following : Unix username: david NT username: david Account Flags: [U ] User SID: S-1-5-21-215069222-2822928016-2390355089-1016 Finding user

Hi, I am running a couple of Samba / LDAP servers. While they all do work fine, I get a message like this on all of them when I run pdbedit -L -v: Unix username: administrator NT username: administrator Account Flags: [UX ] User SID: S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-21000 init_group_from_ldap: Entry found for group: 512 lookup_global_sam_rid:

Hi, last Saturday we reinstalled our fileserver to setup redundancy using DRBD and Heartbeat. We also upgraded Samba to 3.0.23c, which is acting as a PDC. We are using OpenLDAP to store accounts. I populated the OpenLDAP database using a LDIF file that I created on the old server before shutting it down. I also transfered all Samba tdb files to the new server. Everything went pretty

Hello, I'm running a setup with 3 DCs, all Samba 4.5.12, Debian Stretch (is patched for CVE-2018-1057, "samba_CVE-2018-1057_helper" been used). Probably unrelated to the upgrade and patch for CVE-2018-1057, there's a new problem coming up. RSAT fails to start/connect, complaining about RPC-Server unavailablility. On the DCs I've tried with smbclient and get the following:

seems removing idmap settings from smb.conf on both DCs having them has fixed it. smbclient and ADUC work as expected, now. Thank you! > I'm running a setup with 3 DCs, all Samba 4.5.12, Debian Stretch (is > patched for CVE-2018-1057, "samba_CVE-2018-1057_helper" been used). > > Probably unrelated to the upgrade and patch for CVE-2018-1057, there's > a new

On 08/11/15 11:08, Jonathan Hunter wrote: > Hi, > > On 8 November 2015 at 10:49, Michael Adam <obnox at samba.org> wrote: >> This is how it works in rsync: > [...] >> I have always used rsync to replicate the sysvol. >> And always used local xids. But being mainly a >> file-server guy, I have also not managed many Samba >> AD/DC environments. So I am

Hi, On 8 November 2015 at 10:49, Michael Adam <obnox at samba.org> wrote: > This is how it works in rsync: [...] > I have always used rsync to replicate the sysvol. > And always used local xids. But being mainly a > file-server guy, I have also not managed many Samba > AD/DC environments. So I am really more than willing > to learn from others' experience here. This

Replying to my own post - I can reset the mappings by "net cache flush", and this then persists for a while, but ultimately it ends up being overwritten somehow. I'm no longer sure if this is related to files owned by the old UID - because I've since tried to chown all of these, and this is still happening - but I guess I may have missed some, perhaps. On 11 June 2015 at 12:40,

On 15:27:22 wrote Rowland Penny: > On 08/11/15 11:08, Jonathan Hunter wrote: > > Hi, > > > > On 8 November 2015 at 10:49, Michael Adam <obnox at samba.org> wrote: > >> This is how it works in rsync: > > [...] > > > >> I have always used rsync to replicate the sysvol. > >> And always used local xids. But being mainly a >

Hello group, I have 2 Samba PCDs w/ LDAP + winbind called FILESERVER and FUNDUS-SRV for the domains PROFICON and FUNDUS, respectively. In PROFICON I created a trust account for FUNDUS using net rpc trustdom add FUNDUS <passwd> -U proficon\\administrator which creates the LDAP entry: dn: uid=FUNDUS$,ou=Computers,dc=office,dc=proficon,dc=sk uid: FUNDUS$ sambaSID:

I *think* I may have encountered a bug, or a feature, in the idmap/winbind area. I have recently added rfc2307 attributes to my AD, and am in the process of switching over. This means that I still have (unintentionally) some files/directories/etc. around with old UIDs e.g. 3000007, rather than my rfc2307 specified UIDs. What I am seeing is that the SID2XID mapping is initially correct for a