Displaying 20 results from an estimated 600 matches similar to: "use of ‘idmap_ldb:use rfc2307 = yes’ in DCs"
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
The question is, if without the option "use idmap_ldb:use rfc2307 =
yes"? I will be able to set the uid, uidNumber, unixHomeDirectory and
gid on the DC, as I can do it now?
NAVI Sp. z o.o.
Promienista 5/1
60-288 Pozna?
mobile: +48609769035
phone: +48616622881
fax: +48616622882
http://www.navi.pl
On 2024-06-20 12:32, Luis Peromarta via samba wrote:
> This looks OK, and is a member
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
On Thu, 20 Jun 2024 12:25:29 +0200
Olaf Fr?czyk via samba <samba at lists.samba.org> wrote:
> Hello,
>
> Why is it said that it affects only if you have fileserver on DC?
>
> I use uid, uidNumber, unixHomeDirectory for users and gid for groups.
> This attributes are defined in samba DC.
>
> Then I have another samba server that works as fileserver, and I have
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
Hello,
Why is it said that it affects only if you have fileserver on DC?
I use uid, uidNumber, unixHomeDirectory for users and gid for groups.
This attributes are defined in samba DC.
Then I have another samba server that works as fileserver, and I have
this in config:
?? idmap config * : backend = tdb
??? idmap config * : range = 20000-20999
??? idmap config NAVIDOM:backend = ad
???
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
I use uids from this range for many, many years, since samba 3. :)
And I want/need to use this range - to change it now would be a mess.
And I need to be able to set them manually, not in an automatic way.
By server I mean a domain member server.
So on samba DC I have: "idmap_ldb:use rfc2307 = yes"
And on a samba domain member server (that serves files to clients) I have
idmap
2024 Jun 20
2
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
I tried already, feedback welcome and this is all free to use anywhere else.
http://samba.bigbird.es/doku.php?id=samba:no-need-for-use-rfc2307
LP
On Jun 20, 2024 at 10:19 +0100, samba at lists.samba.org <samba at lists.samba.org>, wrote:
>
> We should then document 'idmap_ldb:use rfc2307'
> to say it allows the use of uidNumber & gidNumber attributes on a Samba
>
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
Yes.
The rf2307 attributes are part of the Samba AD schema.
You don?t need the line in the DC unless under very exceptional circumstances.
If you are not sure if you need the line, this means you don?t need the line. It will make your life easier.
LP
On Jun 20, 2024 at 11:40 +0100, Olaf Fr?czyk <olaf at navi.pl>, wrote:
>
> The question is, if without the option "use
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
On Thu, 20 Jun 2024 12:59:58 +0200
Olaf Fr?czyk via samba <samba at lists.samba.org> wrote:
> I use uids from this range for many, many years, since samba 3. :)
Which unfortunately was a bad idea, using Samba IDs that start at
'1000' means that you cannot have ANY local users. What happens if you
have AD problems and your users & groups cannot be resolved from AD,
how do you
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
On 2024-06-20 13:13, Rowland Penny via samba wrote:
> On Thu, 20 Jun 2024 12:59:58 +0200
> Olaf Fr?czyk via samba <samba at lists.samba.org> wrote:
>
>> I use uids from this range for many, many years, since samba 3. :)
> Which unfortunately was a bad idea, using Samba IDs that start at
> '1000' means that you cannot have ANY local users. What happens if you
>
2017 May 10
1
Samba 4.6.0 - Domain admin can't list nor access shares on file server
On 5/10/2017 6:06 PM, Rowland Penny via samba wrote:
> On Wed, 10 May 2017 17:47:37 +0200
> Olaf Frączyk via samba <samba at lists.samba.org> wrote:
>
>> Hello,
>>
>> I have domain NAVIDOM.
>>
>> There is also a fileserver that has joined the domain (both file
>> server and DC are samba 4.6.0).
>>
>> If I try to connect as
2017 Mar 11
4
samba 4.6.0 dc provisioning fails with exception
Hello,
I have a problem with samba provisioning as DC. CentOS 7, built from
tarball using samba howto.
Below is the output. I would have filled bug report, but the "New
Account" in bugzilla is not working also :(
[root at dc samba-4.6.0]# samba-tool domain provision --use-rfc2307 --realm
navidom.office.navi.pl --domain NAVIDOM --server-role dc --adminpass
DuDu778$$# --dns-backend
2017 May 10
2
Samba 4.6.0 - Domain admin can't list nor access shares on file server
Hello,
I have domain NAVIDOM.
There is also a fileserver that has joined the domain (both file server
and DC are samba 4.6.0).
If I try to connect as NAVIDOM\Administrator, I cannot access the file
server (from Linux and Windows):
[root at dc var]# smbclient -U Administrator -L fileserv
Enter NAVIDOM\Administrator's password:
session setup failed: NT_STATUS_ACCESS_DENIED
I can do it as
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
On 2024-06-20 14:04, Rowland Penny via samba wrote:
> On Thu, 20 Jun 2024 13:49:41 +0200
> Olaf Fr?czyk via samba <samba at lists.samba.org> wrote:
>
>> This samba uidNumbers are from times, when local linux users started
>> from 500 and I assumed that starting 1000 for samba will be enough,
>> this was 20 years ago or more.
> Yes, some distros did start IDs
2024 Jun 20
1
use of ‘idmap_ldb:use rfc2307 = yes’ in DCs
On Thu, 20 Jun 2024 13:49:41 +0200
Olaf Fr?czyk via samba <samba at lists.samba.org> wrote:
>
> On 2024-06-20 13:13, Rowland Penny via samba wrote:
> > On Thu, 20 Jun 2024 12:59:58 +0200
> > Olaf Fr?czyk via samba <samba at lists.samba.org> wrote:
> >
> >> I use uids from this range for many, many years, since samba 3. :)
> > Which unfortunately
2017 Mar 11
0
samba 4.6.0 dc provisioning fails with exception
Hello,
I found the cause. It was the default kerberos config on CentOS:
/etc/krb5.conf
Please add to the wiki page:
https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller
that before provisioning we should remove this file.
It wasn't confusing only for me, as the resolution I found was in bugzilla:
https://bugzilla.samba.org/show_bug.cgi?id=11573
2019 Aug 07
1
difference in behaviour of --filter --delete: cmdline vs. file
Hello,
I want to avoid transferring a file which is present both on the source
tree and on the target tree when calling rsync with -a --delete.
mkdir -pv src/ dst/
echo file1 > src/file
echo file2 > dst/file
rsync -navi --delete --exclude file src/ dst/
works as expected. The file is not transferred nor is it deleted at
the receiver.
rsync -navi --delete --filter '- file' src/
2015 Apr 02
2
SMBC_LINK directory entity type
Hello,
I'm trying to write a smb client using the libsmbclient library but I
don't know how to handle the SMBC_LINK type of smbc_dirent, which is
defined in libsmbclient.h.
I've grepped through the samba source code and it doesn't seem to appear
anywhere except the mentioned header and examples.
Can I safely assume there are no files/directories of such a type?
Thanks,
2009 Dec 04
3
Data loss (corruption with rsync)
Hello,
I just rsync'd my 1TB partitions formated with jfs filesystem
containing ~720GB data. I saw -3G difference between source and
destination which made me suspect possible dataloss. Also I had
experienced loss of integrity on my previous copies but I did not find
the cause until now.
As command line I used following:
sh-3.2# rsync --verbose --sparse --append-verify --fuzzy --progress
2010 Nov 08
3
Flash plugin not working
Hi,
I have a fresh install of CentOS 5.5, with a minimal GNOME desktop. I
configured RPMForge as third party repo.
I updated everything first, then installed flash-plugin. (And yes, I
restarted Firefox... :oD). All I see when I try to see some things Flash
on the Internet, like Youtube or the likes, I get... nothing. The space
remains white. Sometimes a black square will appear, sometimes it
2012 Apr 05
3
Problem with polish characters and sieve fileinto
Hi,
I have problems with sieve fileinto and polish characters in folder names:
# rule:[??????????????????]
elsif anyof (header :contains "Subject" "??????????????????")
{
fileinto "INBOX/&AQUBBwEZAUIBRADzAVsBegF8AQQBBgEYAUEBQwDTAVoBeQF7-";
}
dovecot log:
Apr 5 15:17:42 mailer dovecot: lmtp(54203, test at test1.com):
rmHVJHabfU+70wAA9hAjDg: sieve:
2003 Jun 29
2
rpcclient returns NT_STATUS_NO_SUCH_DEVICE on adddriver
Hi,
samba 2.2.8a freshly compiled
cups 1.1.19final-1 (debian)
while using cupsaddsmb, all runs well until adddriver, when rpcclient
returns a cryptic NT_STATUS_NO_SUCH_DEVICE. I've followed the
SambaPrintHowto 3.0 from 7.11.6.1 to 7.11.6.6, and it fails on the
latest as well.
Here is some more information.
===8<===
cupsaddsmb -a -v
Running command: smbclient //localhost/print\$ -N