Displaying 20 results from an estimated 400 matches similar to: "Samba 4 "TKEY is unacceptable" driving me NUTS!"
2019 Apr 17
2
Is possible use BIND9 as DNS Back End on a new Samba DC?
Rowland,
I've done almost all permissions change, I forgot bind-dns directory. Now,
the named service still doesn't start and journalctl -xe showed me that
this occurs because permission denied to run dlz_bind9_9.so. I've checked
out and the lib and directory /usr/local/samba/lib/bind9/ have execute
permission to named group. The output of ls command, journalctl -xe and
2013 Aug 20
1
chmod + remote save denied = file wiped?
I have a SerNet Samba 4.0.8 AD DC running on CentOS 6.4 (newdc)
replicating from a W2K3 DC (olddc). newdc also has a test share.
I'm experiencing something strange whereby chmod and then an attempted
file save causes a shared file to become zero bytes (despite the save
not being blank, and also being denied):
At olddc:
1) open \\newdc\testshare\yay.txt
At newdc:
$ ls -l
total 8
2013 Aug 20
1
AD DC eventually not browsable without restart
I have a SerNet Samba 4.0.8 AD DC running on CentOS 6.4 (newdc)
replicating from a W2K3 DC (olddc). When I first launch Samba using
`sudo samba`, I can go to the Windows server and browse to \\newdc in
Explorer, and I see mytestshare, netlogon, printers, sysvol, and
"Printers and Faxes".
After a while (I'm not sure how long precisely, but under 24 hours) I
could not navigate
2017 Aug 26
0
DC Upgrade from 4.1.7 to 4.6.7
On Sat, 26 Aug 2017 11:28:00 +0400
HB via samba <samba at lists.samba.org> wrote:
> > -----Message d'origine-----
> > De : samba [mailto:samba-bounces at lists.samba.org] De la part de
> > Rowland Penny via samba
> > Envoyé : lundi 21 août 2017 16:34
> > À : samba at lists.samba.org
> > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7
> >
2013 Aug 23
0
CUPS working but errors from Windows clients accessing printer
Hi,
On CentOS 6.4 (newdc), I have CUPS 1.4.2-50.el6_4.5 installed, can
access its web interface. There I set up our main shared printer, an
OCE Imagistics cm2520, and successfully printed a test page.
With SerNet Samba 4.0.9 on the same box configured every which example
way I could find, I cannot seem to get it to the point where
double-clicking the printer in Windows (W2K3, OLDDC) opens
2017 Jan 27
0
samba 4.4
I'm trying to upgrade our old DC's from samba 4.2 to samba 4.4. Rather
than upgrade in-place, I am creating new DCs and then joining them. This
generally seems to work as expected, except outbound replication seems to
fail.
[root at newDC samba-4.4.4]# samba-tool drs replicate newDC oldDC CN=Configuration,DC=ad,DC=mydomain,DC=com -U Administrator
Replicate from oldDC to newDC was
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine-----
> De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland
> Penny via samba
> Envoyé : samedi 26 août 2017 12:00
> À : samba at lists.samba.org
> Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7
>
...
> On Sat, 26 Aug 2017 11:28:00 +0400
> > Hi,
> >
> > I have begun to add a new 4.6.7 DC (following
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine-----
> De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland
> Penny via samba
> Envoyé : lundi 21 août 2017 16:34
> À : samba at lists.samba.org
> Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7
>
> On Mon, 21 Aug 2017 15:52:01 +0400
> HB via samba <samba at lists.samba.org> wrote:
>
> > Hello all,
2013 Aug 16
2
share permissions
I have a share setup on a Samba 4.0.8 / CentOS 6.4 box that is
successfully replicating with a W2K3 server. I'm following the HOWTO
here: https://wiki.samba.org/index.php/Setup_and_configure_file_shares
[mytest]
path = /home/me/mytestshare <-- with or without trailing slash
read only = No
On the W2K3 box, I can browse to \\newdc and I see my test share listed
there. I can also see
2014 Aug 14
1
Samba 4.1.6 vs Win2008R2 FSMO roles
Hi,
we're using Zentyal 3.4/Samba 4.1.6 on two machine for our AD domain.
We have to test the domain in "pure" microsoft environment, because a third
party storage system.
So I added DC and DNS role to one of our windows 2008R2, and joined it to
our domain. Everything's fine at this point.
Then I wanted transfer the 5 FSMO role to windows. Every role transferred
successfully,
2014 Aug 27
0
FSMO roles
After accidentally destroying my primary DC which held all of the FSMO
roles, I am unable to show any roles, or sieze the naming role. I
initialy tried to sieze --role=all, and it failed, but by doing
them individually I was able to seize them all except for the
naming role. Any suggestions on how to fix this?
# samba-tool fsmo show -d 9
<removed generic debug info>
pm_process()
2013 Sep 26
1
Failed FSMO transfer - role naming - samba 4.0.9
Hi,
------------------------------------------------------------
root at samba4:~# samba-tool fsmo show
InfrastructureMasterRole owner: CN=NTDS
Settings,CN=SAMBA4,CN=Servers,CN=Primeiro-site-padrao,CN=Sites,CN=Configuration,DC=UDOPIAUI,DC=NET,DC=BR
RidAllocationMasterRole owner: CN=NTDS
Settings,CN=SAMBA4,CN=Servers,CN=Primeiro-site-padrao,CN=Sites,CN=Configuration,DC=UDOPIAUI,DC=NET,DC=BR
2014 Nov 05
2
Lost DC with FSMO-Rolls
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I lost my DC with all fsmo-roles. I try to "seize" the roles to
another DC. It worked four out of five roles:
root at SVL-V-AD1:~# samba-tool fsmo seize --role=rid
Attempting transfer...
Transfer unsuccessful, seizing...
FSMO seize of 'rid' role successful
root at SVL-V-AD1:~# samba-tool fsmo seize --role=pdc
Attempting
2013 Sep 22
0
gpresult returns "ERROR: The RPC server is unavailable."
Hi,
I have a CentOS 6.4 box running SerNet Samba 4.0.9 as an AD DC
replicating from a W2k3 box.
If I run "gpresult /s OLDDC /user MYDOM\Me" on a command prompt on
OLDDC, I get a normal output, listing which GPOs are applied.
If I run "gpresult /s NEWDC /user MYDOM\Me" in the same place, I get
"ERROR: The RPC server is unavailable." This is after a fresh restart
2014 Apr 25
1
Moving to Bind from internal Ubuntu Server
Hello
I'm trying to move to Bind from internal DNS. Internal DNS sometimes
does not answer for clients with forwarded from another one records. It
serves only local addreses when there is high traffic.
When i start bind is see some errors:
-----------------------------------
Apr 25 13:50:35 PrimaryDC named[7726]: sizing zone task pool based on 5
zones
Apr 25 13:50:35 PrimaryDC
2014 Aug 19
0
Samba4 AD with bind DNS / TKEY is unacceptable
Solved that by chowing the file used on /etc/bind/named.conf.options >>
tkey-gssapi-keytab "/var/lib/samba/private/dns.keytab";
chown bind.root /var/lib/samba/private/dns.keytab
I am using debian.
2014 Feb 12
1
TKEY is unacceptable
Samba 4.1.1 using BIND_DLZ (bind-9.9.1-0.1.P2) on CentOS 6.5 x86_64.
I have two domain controllers, dc-1 and dc-2, which each have three
network interfaces. Selinux is in permissive mode, and iptables is off.
One interface on each dc is to be shut down. So, on dc-1, I do:
# nsupdate -g
update delete europa.icse.cornell.edu A 192.168.3.250
update delete europa.icse.cornell.edu A 192.168.3.251
2015 Aug 06
0
2nd DC, internal DNS: dns_tkey_negotiategss: TKEY is unacceptable
On 2015-08-06 18:55, Roel van Meer wrote:
> Hi everyone,
>
> I'm testing with a Samba4 AD network, and I have some problems with
> DNS on the second DC, with which I could use a bit of your help.
>
> I have an AD with two DC's, both Samba 4.2.3. On the first DC,
> samba_dnsupdate works fine. With stock 4.2.3 I get the error
>
> "TSIG error with
2015 Dec 30
0
dns_tkey_negotiategss: TKEY is unacceptable
On 30/12/15 18:19, Carlos A. P. Cunha wrote:
> Hello!
> I've got this error
> dns_tkey_negotiategss: TKEY is unacceptable
>
> when running samba_dnsupdate --verbose
>
> With this error dynamic entries stopped working as Type A machines
> that entered in the field or entry to a new DC.
>
> Already tried the step described here
>
>
2015 Dec 30
0
dns_tkey_negotiategss: TKEY is unacceptable
On 30/12/15 18:19, Carlos A. P. Cunha wrote:
> Hello!
> I've got this error
> dns_tkey_negotiategss: TKEY is unacceptable
>
> when running samba_dnsupdate --verbose
>
> With this error dynamic entries stopped working as Type A machines
> that entered in the field or entry to a new DC.
>
> Already tried the step described here
>
>