samba - Nov 2020 - AD Running - Gui with strange messages like "domain does not exist*

Hello

My AD on Samba now are running! Thanks!

# samba-tool -V

samba-tool: no such subcommand: -V

4.13.2-Debian

 

In the meantime Joining Computers and Servers, creat User Account and was
successful to logon, NOce!

 

One question, that confusing, to Manage this Samba AD using the Windows
"Active Directory Users and Computers (GUI)" application

Here if add a new User or jump to the Register
"Account/Members/Profiel/Sessions" and and .....appair any time the
message.

 

--

The specified domain either does not exist or could not be contaced

--

the Pre-Windows 2000 domain name for the user cannot be displayed

--

the following active Directory Domain Services error occurred the

The specified domain either does not exist or could not be contaced

--

Cannot connect to any Domain, referesh or try again when connection us
available

--

Cannot find an available server in the Caloro domain, that is running the
Active Directory Web Service (ADWS)

--

If try to open "Group Policy-Management" appair the message

- the spedified domain either does not exist or could not be contacted

--

 

The joining are running without problems... please or its this App now
obsoled?

With witch app you will administrate new Accounts or Users?

 

Thanks for any possible update!!

Regards

Mauri

On 04/11/2020 10:36, Maurizio Caloro via samba wrote:
> Hello
>
> My AD on Samba now are running! Thanks!
>
> # samba-tool -V
>
> samba-tool: no such subcommand: -V
>
> 4.13.2-Debian
Strange, that works for myself, but I am still using 4.12.x

root at dc4:~# samba-tool -V
4.12.8-Debian
> Cannot find an available server in the Caloro domain, that is running the
> Active Directory Web Service (ADWS)
>
That is the operative line, a Samba AD DC doesn't run ADWS, I think 
someone is working on it, but until then you will have to use other Unix 
based tools. Such tools are 'samba-tool', LAM, personal scripts, ADMan 
(https://gitlab.com/JonathonReinhart/adman/) or the upcoming cockpit module.

There are other tools available.

Rowland

On 04/11/2020 14:40, Maurizio Caloro wrote:
> On 04/11/2020 10:36, Maurizio Caloro via samba wrote:
>> Hello
>> My AD on Samba now are running! Thanks!
>>
>> # samba-tool -V
>> samba-tool: no such subcommand: -V
>> 4.13.2-Debian
> Strange, that works for myself, but I am still using 4.12.x
>
> root at dc4:~# samba-tool -V
> 4.12.8-Debian
>
>> Cannot find an available server in the Caloro domain, that is running
>> the Active Directory Web Service (ADWS)
>>
>>> That is the operative line, a Samba AD DC doesn't run ADWS, I
think
> someone is working on it, but until then you will have to use other Unix
> based tools. Such tools are 'samba-tool', LAM, personal scripts,
ADMan
>>> (https://gitlab.com/JonathonReinhart/adman/) or the upcoming
cockpit
> module.
>
>>> There are other tools available.
>>>
>>> Rowland
> ok after complete new installation of Debian, Bind and Samba-AD-DC I have
> here the stange error messages that mentioned in the first step
>
> samba-tools domain provision
>
> Systemctl status samba-ad-dc
>
>             +-608 /usr/sbin/smbd -D --option=server role check:inhibit=yes
> --foreground
>             L-817 /usr/sbin/smbd -D --option=server role check:inhibit=yes
> --foreground
What is the full output of 'systemctl status samba-ad-dc' ? does it 
mention winbind ?

Rowland

On 04/11/2020 15:42, Maurizio Caloro wrote:
> Yes Winbind ist mentoined.....
OK, just checking, it has been known for winbind to be not
installed.
> Nov 04 15:38:38 debian samba[950]: [2020/11/04 15:38:38.756316,  0]
../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler)
> Nov 04 15:38:38 debian samba[950]:   /usr/sbin/samba_dnsupdate: ERROR:
Record already exist; record could not be added. zone[smbtest]
name[_ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones]
>
> and why i have here the Samba_DnsUpdate errors?? This configu run with the
Bind9_DLZ config
It has nothing to do with Bind9 and it isn't really an error, the record 
cannot be added because it already exists. You may be receiving the 
message because you have the loglevel set too high.

Rowland