Displaying 20 results from an estimated 7000 matches similar to: "Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed"
2017 Dec 04
2
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Il giorno lun, 04/12/2017 alle 13.17 +0100, Christian Naumer via samba
ha scritto:
> Is
>
> /var/lib/samba/bind-dns/
>
> accessible by bind?
Yes, and selinux is disable
[ root at server-addc ~]# find /var/lib/samba/bind-dns/ -ls
3149158 0 drwxrwx--- 3 root named 95 dic 4 14:03 /var/lib/samba/bind-dns/
111 0 drwxrwx--- 3
2017 Dec 04
3
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Il giorno lun, 04/12/2017 alle 12.07 +0000, Rowland Penny via samba ha
scritto:
> Is the DHCP server updating the records for you ?
Yes, but for now the problem is not dhcp (see follow)
> If so, you need to stop the windows clients trying to update their
> own records, they don't own them.
I have the problem when join to domani via samba on another server, or
when I run
2017 Dec 04
2
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Il giorno lun, 04/12/2017 alle 11.29 +0000, Rowland Penny via samba ha
scritto:
> Try changing the 'options' of named.conf to this:
Thanks Rowland
Integrated your suggested changes and restart samba and named
Now my named.conf is this[1], but none is change:
[ root at server-addc ~]# samba_dnsupdate --all-names --fail-immediately
update failed: REFUSED
dic 04
2017 Dec 04
2
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
On Mon, 04 Dec 2017 16:57:15 +0100
Dario Lesca via samba <samba at lists.samba.org> wrote:
> Il giorno lun, 04/12/2017 alle 16.00 +0100, Dario Lesca via samba ha
> scritto:
> > The samba command
> >
> > samba_dnsupdate --verbose --all-names --fail-immediately
> >
> > not work
>
>
> Following this howto,
>
2017 Dec 04
0
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Is
/var/lib/samba/bind-dns/
accessible by bind?
Regards
Christian
Am 04.12.2017 um 11:35 schrieb Dario Lesca via samba:
> I have setup on Fedora 27 server a AD-DC samba server + bind + dhcp.
>
> All seem work fine: I can join to domain, add/remove dns records with
> samba-tools, access to shared folder, use MS Management Console on
> Win7, ecc
>
> But when I join
2017 Dec 04
4
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Il giorno lun, 04/12/2017 alle 14.48 +0000, Rowland Penny via samba ha
scritto:
>
>
> The cure is to STOP your windows clients trying to update their own
> records.
Yes, this is true, on windows I will stop this service.
But my problem now is another
The samba command
samba_dnsupdate --verbose --all-names --fail-immediately
not work
It's possible to resolve this
2017 Dec 04
0
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
On Mon, 04 Dec 2017 15:34:37 +0100
Dario Lesca via samba <samba at lists.samba.org> wrote:
> Il giorno lun, 04/12/2017 alle 12.07 +0000, Rowland Penny via samba ha
> scritto:
> > Is the DHCP server updating the records for you ?
>
> Yes, but for now the problem is not dhcp (see follow)
>
> > If so, you need to stop the windows clients trying to update their
>
2017 Dec 04
0
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Il giorno lun, 04/12/2017 alle 16.00 +0100, Dario Lesca via samba ha
scritto:
> The samba command
>
> samba_dnsupdate --verbose --all-names --fail-immediately
>
> not work
I have add '-d 9' to dlz section
dlz "AD DNS Zone" {
# For BIND 9.11.x
database "dlopen /usr/lib64/samba/bind9/dlz_bind9_11.so -d 9";
};
And this is
2017 Dec 04
2
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
On Mon, 04 Dec 2017 16:31:16 +0100
Dario Lesca via samba <samba at lists.samba.org> wrote:
> Il giorno lun, 04/12/2017 alle 16.00 +0100, Dario Lesca via samba ha
> scritto:
> > The samba command
> >
> > samba_dnsupdate --verbose --all-names --fail-immediately
> >
> > not work
>
> I have add '-d 9' to dlz section
>
> dlz
2017 Dec 04
0
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
On Mon, 04 Dec 2017 12:56:19 +0100
Dario Lesca via samba <samba at lists.samba.org> wrote:
> Il giorno lun, 04/12/2017 alle 11.29 +0000, Rowland Penny via samba ha
> scritto:
> > Try changing the 'options' of named.conf to this:
>
> Thanks Rowland
>
> Integrated your suggested changes and restart samba and named
>
> Now my named.conf is this[1], but
2017 Dec 04
0
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Il giorno lun, 04/12/2017 alle 16.00 +0100, Dario Lesca via samba ha
scritto:
> The samba command
>
> samba_dnsupdate --verbose --all-names --fail-immediately
>
> not work
Following this howto,
https://wiki.samba.org/index.php/Dns_tkey_negotiategss:_TKEY_is_unacceptable#Verifying_That_the_BIND_AD_Account_Exists_for_the_DC
I have try this:
[ root at server-addc
2017 Dec 04
0
Samba 4.7.2 + bind on Fedora 27: samba_dlz: spnego update failed
Am 04.12.2017 um 17:19 schrieb Rowland Penny via samba:
> On Mon, 04 Dec 2017 16:57:15 +0100
> Dario Lesca via samba <samba at lists.samba.org> wrote:
>
>> Il giorno lun, 04/12/2017 alle 16.00 +0100, Dario Lesca via samba ha
>> scritto:
>>> The samba command
>>>
>>> samba_dnsupdate --verbose --all-names --fail-immediately
>>>
2018 Nov 22
2
How to set same UID and GID for ADDC server and all Member server
I have setup a ADDC Samba server and a winbind member server
I have see that same user have UID/GID different from ADDC and
member server
# Addc (Fedora 29)[root at s-addc ~]# id d.lescauid=3000023(DOM\d.lesca)
gid=100(users)
gruppi=100(users),3000023(DOM\d.lesca),3000009(BUILTIN\users)[
root at s-addc ~]# rpm -q sambasamba-4.9.2-0.fc29.x86_64
# Member (Centos7)[root at s-dati ~]# id
2019 Sep 01
2
Problem to access from Win to Win after classicupdate to Samba DC 4.10.7
I have do a classicupdate from a NT4 style domain to Samba DC 4.10.7
BIND_DLZ without (apparently) problem
All seem work fine, access to PC work, join or re-join a PC to domain
work, access from a Linux samba member server to Win7 PC work, access
from Win7 to samba member server work.
But I cannot access from a PC with win7 to another PC with win7.
If I try to access from win7-0 to win7-1 via
2017 Mar 07
2
Samba 4.4.4: ACLs not work property with recycle vfs object enable
Samba file server (Server role: ROLE_DOMAIN_MEMBER) joined to Win2008
ADDC
I have a strange problem with ACLs and "vfs object = recycle" enabled
This is my share entry
> [dati]
> comment = Cartella Dati x tutti
> path = /u/samba/dati/
> read only = no
>
> Veto files = /*.pst/*.ost/
>
> inherit acls = yes
>
2017 Nov 06
5
Failed to find domain 'NT AUTHORITY'
Hello,
I recently set up a new software to backup samba share.
This software ( https://github.com/borgbackup/borg ) run on file server as
root cron script during the night and save file on external NAS.
The problem I have is that for each file copied from
samba share to external NAS, winbindd log an error
such this to samba.log.winbindd and /var/log/messages
[2017/11/06 11:05:16.747449, 0]
2014 Mar 14
1
Replying to Posts
On Thu, March 13, 2014 15:32, Kevin Larsen wrote:
>> On 13/3/14 6:27 pm, Eric Wieling wrote:
>> > This is an example of why I top post. Who wrote what?
>>
+1-1 = 0
I do not care about where people put their replies so long as I can figure out
who is answering what. What I do not like to read is this interminable
religious dogma about the 'natural' order of
2016 Dec 26
5
DDNS with Bind
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I try to set up a ADDC with bind9 and dhcp-Server for dynamic
DNS-updates. I followd the wiki:
https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_wi
th_BIND9
My problem is, that the PTR Record will not be updated, because the
script is using the wrong reverse-zone:
- ---------------------
Dez 26 17:30:05 addc-01 named[512]:
2020 Apr 30
7
bind9 refuses to start -> zone has no NS records
Hi,
I have to add a second DC to a Zone.
I use the sernet packages Version 4.11 on a debian 10 host.
The bind refuses to start:
root at addc-zone02:~# systemctl status bind9
? bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-04-30 14:51:58 EEST; 5s ago
Docs:
2017 Dec 06
3
MMC issue
Am 06.12.2017 um 10:14 schrieb Rowland Penny via samba:
> On Tue, 5 Dec 2017 15:39:25 -0700 (MST)
> Mariusz80 via samba <samba at lists.samba.org> wrote:
>
>> Well permisions are working fine but, if i create for example "new
>> folder" then the owner is root and what about the main problem with
>> mmc.
>>
>
> New files/directories will be