Displaying 20 results from an estimated 3000 matches similar to: "Samba 4.11.6 cannot JOIN - 'Could not find machine account'"
2020 Feb 15
0
Samba] Samba 4.11.6 cannot JOIN - 'Could not find machine account'
On 15/02/2020 20:08, Rick Hollinbeck wrote:
> Andrew and Rowland - thank you for your input.
>
> I've actually made some progress finally!
>
> I double checked the items mentioned in this old thread describing solving the same
> behavior:
> https://www.spinics.net/lists/samba/msg148337.html
>
> One little thing was different in my Windows Server's DNS
> (which
2020 Feb 07
1
Samba 4.11.6 cannot JOIN - 'Could not find machine account'
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
<title></title>
<meta http-equiv="content-type" content="text/html;charset=utf-8"/>
2020 Feb 10
0
Samba 4.11.6 cannot JOIN - 'Could not find machine account'
Hi Rowland,
> Can you try the join command like this:
> samba-tool domain join office.example.com DC -UAdministrator
> --password=TheActualPassword --dns-backend=BIND9_DLZ
> Rowland
When I run samba-tool like this without specifying the server, it chooses the older backup
server that runs Server 2008 (named PE2600).
Joining to this server results in a different error:
....
INFO
2019 Jun 19
0
DLZ Backend DNS Hosed
Hai,
For bind, please to add this for bind if you use bind_DLZ.
How : systemctl edit bind9, or create the file manualy and run systemctl daemon-reload after.
The edit command already does the reload.
# /etc/systemd/system/bind9.service.d/override.conf
[Service]
ExecReload=
But same for you. ;-) as the other list message today. ([Samba] Reverse DNS)
Can you run this for me on the
2024 Jan 21
2
Provisioning new AD Domain Controller
On Sat, 20 Jan 2024 20:31:31 -0500
Mark Foley via samba <samba at lists.samba.org> wrote:
> On Sat Jan 20 16:28:14 2024 Rowland Penny via samba
> <samba at lists.samba.org> wrote:
> >
> > On Sat, 20 Jan 2024 15:44:18 -0500
> > Mark Foley via samba <samba at lists.samba.org> wrote:
> >
> > > After provisioning and testing my new DC offline,
2017 Mar 30
0
" a misconfigured DNS zone" (was Provision new domain keeping users and passwords (Santiago))
On Thu, 30 Mar 2017 08:29:10 -0500
Santiago Londoño Mejía via samba <samba at lists.samba.org> wrote:
> Hello,
> Thank you very much for your reply.
> I changed named.conf And this is the log:
>
> Mar 30 08:23:35 neptuno named[3419]: sizing zone task pool based on 1
> zones Mar 30 08:23:35 neptuno named[3419]: Loading 'AD DNS Zone'
> using driver dlopen Mar 30
2016 Nov 04
0
debugging bind9_DLZ
On Fri, 04 Nov 2016 12:29:42 -0500
Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
> On 2016-11-04 12:07, Rowland Penny via samba wrote:
>
> > On Fri, 04 Nov 2016 11:49:16 -0500
> > Bob of Donelson Trophy <bob at donelsontrophy.net> wrote:
> >
> > On 2016-11-04 11:31, Rowland Penny via samba wrote:
> >
> >
2016 Nov 04
2
debugging bind9_DLZ
On 2016-11-04 12:07, Rowland Penny via samba wrote:
> On Fri, 04 Nov 2016 11:49:16 -0500
> Bob of Donelson Trophy <bob at donelsontrophy.net> wrote:
>
> On 2016-11-04 11:31, Rowland Penny via samba wrote:
>
> <<<<< cut >>>>>>>>
>
> root at dtdc03:~# samba-tool dns zonelist dtdc03
> 3 zone(s) found
>
> pszZoneName
2016 Nov 04
1
debugging bind9_DLZ
On 2016-11-04 12:43, Rowland Penny via samba wrote:
> On Fri, 04 Nov 2016 12:29:42 -0500
> Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
>
> On 2016-11-04 12:07, Rowland Penny via samba wrote:
>
> On Fri, 04 Nov 2016 11:49:16 -0500
> Bob of Donelson Trophy <bob at donelsontrophy.net> wrote:
>
> On 2016-11-04 11:31, Rowland Penny via
2019 Jun 20
0
DLZ Backend DNS Hosed
And, BTW, right now, I am able to see my problem via the following 3 ways...
1) Through Windows DNS Manager, I cannot add, change or delete any DNS records from:
mycompany.loc
samdom.mycompany.net
mycompany.net
I *can* add, change and delete DNS records from:
_msdcs.samdom.mycompany.net
mycompany.com
7.168.192.in-addr.arpa
5.168.192.in-addr.arpa
3.168.192.in-addr.arpa
2017 Apr 06
2
" a misconfigured DNS zone" (was Provision new domain keeping users and passwords (Santiago))
Hello,
Thank you very much for your response, sorry for the delay
I can not list the zones, get this error:
¿What else could I verify so I did not reinstall the domain?
Best regards,
Santiago.
Password for [PRAGMA\ADMINISTRATOR]:
ERROR(runtime): uncaught exception - (9717, 'WERR_DNS_ERROR_DS_UNAVAILABLE')
File
2017 Mar 15
0
Problems with replication and dns
On Wed, 15 Mar 2017 10:03:59 -0500
Santiago Londoño Mejía <santiago.londono at pragma.com.co> wrote:
> Hello,
> Thank you very much for your reply.
> I have configured bind using the dlz backend and these are the
> results.
>
> named log:
>
> Mar 15 09:39:41 neptuno named[13166]: sizing zone task pool based on
> 6 zones Mar 15 09:39:41 neptuno named[13166]:
2019 Jun 21
0
DLZ Backend DNS Hosed
No, this is not needed.
Solution here in this is simple.
search primary.domain.tld # optional extra search domains after the primary.
nameserver IP_AD-DC_OF_THIS_SERVER_FIRST
nameserver IP_AD-DC_others
Run : samba_upgradedns --dns-backend=BIND9_DLZ
And your done, all needed records are fixed/updated.
This goes wrong if the IP of the running server isnt the first and/or if search is setup
2006 Jan 06
0
Windows 2003 and DC Samba
Hi,
Here is my log, does someone know what it means ?
Jan 6 11:20:38 SAMBA1 smbd[3053]: write_socket: Error writing 4 bytes to s
ocket 22: ERRNO = Connexion r??-initialis??e par le correspondant
Jan 6 11:20:38 SAMBA1 smbd[3053]: [2006/01/06 11:20:38, 0] lib/util_sock.c:s
end_smb(647)
Jan 6 11:20:38 SAMBA1 smbd[3053]: Error writing 4 bytes to client. -1. (Co
nnexion r??-initialis??e par le
2006 Mar 16
0
ldap+samba user cannot change his password
Using "ldap password sync=yes" I can modify user password as admin
through "net rpc user password" but if I try to modify it from the user
(net rpc password myuser mypw -U myuser) or from windows (ctrl+alt+del).
I get a timout error:
[2006/03/16 21:52:40, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)
rpc_api_pipe: Remote machine alphacserver pipe \samr fnum
0x70e9returned
2018 Apr 19
0
Share authentication problem
Ok, please post of both servers the smb.conf and tell the samba versions.
You have a misconfiguration in these.
> WARNING: The "idmap gid" option is deprecated
> WARNING: The "idmap uid" option is deprecated
^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "idmap gid"="10000-20000"
> "idmap uid"="10000-20000"
You need something like this
2014 Apr 08
1
FW: DNS record info (samba-tool)
Doh forgot to cc
-----Original message-----
> From:Stuart Naylor <stuartiannaylor at thursbygarden.org>
> Sent: Tuesday 8th April 2014 21:16
> To: G?nter Kukkukk <linux at kukkukk.com>
> Subject: RE: [Samba] DNS record info (samba-tool)
>
> Brilliant, glad about that as zones pretty much done on set up and no worry about a restart.
>
> Great that adding
2005 Nov 29
0
I/O error samba mount point (only with smbfs)
Hi,
I am getting an I/O error while running fsstress on client samba mount point
(only with smbfs)
Can anyone, please look into this problem?
Problem Description:
x370 was configured for samba server & x206f as samba client.
fsstress was running from two samba mount points from client i.e /SAMBA1 (type
cifs) & /SAMBA2 (type smbfs).
There was no load generating on /SAMBA2 & hence
2008 Mar 31
0
Failed to set servicePrincipalNames
When trying to execute "net ads join", I was getting the following message:
"Failed to set servicePrincipalNames. Please ensure that the DNS
domain of this server matches the AD domain,
Or rejoin with using Domain Admin credentials."
A couple of tips to troubleshoot this problem:
1. Do a kinit username@KERBEROS.REALM so that you can get a ticket
opened and not have to
2018 Apr 20
1
Share authentication problem
Hi Rowland,
Thank you very much for your help! The main problem was fixed today -
and i have to apologize for bothering sambalist because it was an
error40 (40cm in front of the PC). In my test enviroment, there was
still an old, non-existing SID on the domdata share, however - after
deleting the access permissions in Windows and adding new, everything
goes fine now. I answered your