Displaying 20 results from an estimated 10000 matches similar to: "inconsistent DNS information, windows domain member issues.."
2016 Jun 05
2
inconsistent DNS information, windows domain member issues..
> -----Ursprüngliche Nachricht-----
> Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von
> Rowland penny
> Gesendet: Sonntag, 5. Juni 2016 12:49
> An: samba at lists.samba.org
> Betreff: Re: [Samba] inconsistent DNS information, windows domain
> member issues..
>
> On 05/06/16 10:05, Jo wrote:
> > I joined a Windows 10 Pro system to my (still
2016 Jun 05
2
inconsistent DNS information, windows domain member issues..
> -----Ursprüngliche Nachricht-----
> Von: Rowland penny [mailto:rpenny at samba.org]
> Gesendet: Sonntag, 5. Juni 2016 17:46
> An: Jo <j.o.l at live.com>
> Cc: 'samba' <samba at lists.samba.org>
> Betreff: Re: AW: [Samba] inconsistent DNS information, windows domain
> member issues..
>
> On 05/06/16 13:43, Jo wrote:
> >> Your DCs really
2019 Apr 05
2
wbinfo isn't working on domain member
Hi Rowland, I made the change you suggested to auto refresh kerberos. It
didn't seem to fix the issue unfortunately, even after a machine
restart. Following your line of reasoning that it is a Kerberos issue, I
then tried to grab a new kerberos ticket on the server in question which
appears to fail though. Perhaps this gives some further insight?
pi at fs1:~ $ kinit administrator at
2020 Jun 11
2
getting no SRV record
On 11/06/2020 12:16, Bob Wooden via samba wrote:
> When I "nslookup". I get:
>
> root@[dchost]:~# nslookup [dchost].[domain].work
> Server:??? ??? 192.168.116.50
> Address:??? 192.168.116.50#53
>
> Non-authoritative answer:
> Name:??? [dchost].[domain].work
> Address: xx.198.245.139
>
> This local active directory is the first I have ever setup with a
2017 Nov 08
2
DC's are unavailable when PDC halted
Hi folks,
there are two Samba4 DC server. The first one is the "PDC", and
after I finished to set up that, I've joined the second one.
There is a Linux client, where I configured the samba, and joined
it to domain as member. Now I see these:
# net ads status -U administrator
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
objectClass:
2016 Jul 19
1
Debian Jessie joining AD as member fails with "The object name is not found."
Hi all!
I had originally been using a DHCP-assigned address. I have now switched to a static IP, but that didn't solve the problem (same error message).
I'm attaching my resolv.conf, nsswitch.conf and krb5.conf files. I have not manually altered either of them, although krb5.conf appears to have been updated by some tool somewhere along the way because my domain is listed as the
2019 Oct 16
2
message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
Hello,
I need help you to understand my error.
I have juste generate samba ad with the following command
samba-tool domain provision --use-rfc2307 --interactive
Realm:? SAMBADOM.CALAIS.FR
Domain [SAMBADOM]:
Server Role (dc, member, standalone) [dc]:? dc
DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE)
[SAMBA_INTERNAL]:? SAMBA_INTERNAL
DNS forwarder IP address (write 'none'
2020 Oct 22
8
new dc does not allow login..?
In installed a new DC (Samba 4.12.8 on Ubuntu 20.4) and initially everything appeared to work smoothly. Now I experience issues:
DCDIAG /s:cobra.samba.lindenberg.one
Directory Server Diagnosis
Performing initial setup:
[cobra.samba.lindenberg.one] LDAP bind failed with error 1326,
The user name or password is incorrect..
With the other DC (still samba 4.11.14 on Ubuntu
2017 Nov 08
2
DC's are unavailable when PDC halted
Hi Rowland,
On Wed, Nov 08, 2017 at 09:45:48AM +0000, Rowland Penny wrote:
> On Wed, 8 Nov 2017 09:24:30 +0100
> Ervin Hegedüs via samba <samba at lists.samba.org> wrote:
>
> > Hi folks,
> >
> > there are two Samba4 DC server. The first one is the "PDC", and
> > after I finished to set up that, I've joined the second one.
>
> I am a
2018 Nov 22
2
Setup a Samba AD DC as an additional DC
which samba version, because i've een reports the 4.8 fails and 4.7 fails but 4.6 should work, and i dont know about 4.9.2
Can you show your /etc/hosts file and /etc/resolv.conf and /etc/krb5.conf
You used :
samba-tool domain join mydomain.com DC -U"MYDOMAIN\administrator" --dns-backend=SAMBA_INTERNAL --option="interfaces=ens2f0"
not wrong, but can you try.
kinit
2019 Oct 16
2
message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
Le 16/10/2019 ? 09:33, Rowland penny via samba a ?crit?:
> On 16/10/2019 07:56, nathalie ramat via samba wrote:
>> Hello,
>>
>> I need help you to understand my error.
>>
>> I have juste generate samba ad with the following command
>>
>> samba-tool domain provision --use-rfc2307 --interactive
>> Realm:?? SAMBADOM.CALAIS.FR
>> Domain
2019 Apr 10
6
chown: changing ownership of 'test': Invalid argument
Hi All,
I have a very weird issue on one of my servers. I think I might just be
missing something quite obviously... I will post the config files at the
bottom
I have a brand new Debian server running as an LXC container
> root at ho-vpn-ctx-ac01:~# lsb_release -a
> No LSB modules are available.
> Distributor ID: Debian
> Description: Debian GNU/Linux 9.8 (stretch)
>
2015 Mar 12
7
samba 4.1.17 on raspberry pi as ad dc - internal dns problems
>Hi, please don't use .local, you say that no apple devices will come
>near, but what about an iphone ? and what about avahi ?
>When you ran configure, you might as well just run it like this: ./configure
>All the rest are defaults and you do not really need debug.
>You only need to alter /etc/nsswitch.conf (yes that's the one) if you
>want/need your users to log into
2016 Jun 06
2
inconsistent DNS information, windows domain member issues..
To regenerate dns.keytab I expect you only need to relaunch
samba_upgradedns --dns-backend=BIND9_DLZ.
If I'm wrong (it happens quiet often) you would have to first launch:
samba_upgradedns --dns-backend=SAMBA_INTERNAL
and then
samba_upgradedns --dns-backend=BIND9_DLZ
Here you should have a dns.keytab.
Now, right issues: dns related files in samba/private must be accessible to
the UNIX user
2014 May 09
1
samba4 : [kerberos part kinit work but no kpasswd
hi,
?
i have recently installed a samba 4 in a DC role.
The distribution is a debian jessie/sid, the version of samba is 4.1.7.
The server is globally working but there is some litle trouble.
on the server itself, i can do a kinit without probleme but if i try a kpasswsd, i obtain the following
?
root at station:/var/log/samba# kinit
Password for administrator at TOTO.FR:
root at
2016 Jun 05
0
inconsistent DNS information, windows domain member issues..
On 05/06/16 13:43, Jo wrote:
>> Your DCs really need to be running at all times, so that replication
>> can work properly, also each DC should use the other for their DNS
>> server, anything unknown to the DNS servers on the DCs should be
>> forwarded to an external DNS that does know or can find out.
> I understand that they need to be up simultaneously for
2018 Nov 27
10
Setup a Samba AD DC as an additional DC
Hai,
I had a quick look.
Barry, can you get this script and run it.
https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh
Then post the results to the list.
It collects all info i need to have a better look.
I have a few ideas, this might be a resolving order problem, i've based on the errors below.
Can you also post the output of bind from the point its
2016 Jul 18
3
Debian Jessie joining AD as member fails with "The object name is not found."
Hi all!
To clarify, it must have been removed from the copy-pasta, but “net ads join -U” did produce a password prompt as expected.
The dig command produced the following:
root at host:~$ dig -t SRV _ldap._tcp.domain.local
; <<>> DiG 9.9.5-9+deb8u6-Debian <<>> -t SRV _ldap._tcp.domain.local
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode:
2016 Jun 05
0
inconsistent DNS information, windows domain member issues..
On 05/06/16 18:25, Jo wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: Rowland penny [mailto:rpenny at samba.org]
>> Gesendet: Sonntag, 5. Juni 2016 17:46
>> An: Jo <j.o.l at live.com>
>> Cc: 'samba' <samba at lists.samba.org>
>> Betreff: Re: AW: [Samba] inconsistent DNS information, windows domain
>> member issues..
>>
2015 Mar 12
5
samba 4.1.17 on raspberry pi as ad dc - internal dns problems
Hey Peter,
many thanks for your reply.
---
regarding .local domains
I know this is regarded by some as bad form, is actively being
discouraged by the samba wiki and can cause problems with
bonjour/zerobla configuration.
I can say for certain that no apple devices will ever come anywhere near
that network and the other drawbacks of .local like getting signed
certs... should never be an issue