similar to: message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log

Displaying 20 results from an estimated 4000 matches similar to: "message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log"

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 Oct 16
2
message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
Le 16/10/2019 ? 11:17, Rowland penny via samba a ?crit?: > On 16/10/2019 09:43, nathalie ramat wrote: >> >> I put the trace of the script : > OK, only two problems, one minor, one possibly catastrophic ;-) >> >> Collected config?? --- 2019-10-16-10:23 ----------- >> >> ???????????? Checking file: /etc/hosts >> >> 127.0.0.1?????? localhost
2019 Oct 16
2
message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
Le 16/10/2019 ? 12:07, Rowland penny via samba a ?crit?: > On 16/10/2019 10:59, nathalie ramat wrote: >> ???????????? Checking file: /etc/samba/smb.conf >> >> # Global parameters >> [global] >> ?????? dns forwarder = 192.168.xx.230 > You cannot forward to the DC itself, it needs to be a dns server > outside the AD dns domain. >> ?????? netbios name =
2019 Oct 16
0
message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
On 16/10/2019 11:33, nathalie ramat wrote: > > > Le 16/10/2019 ? 12:07, Rowland penny via samba a ?crit?: >> On 16/10/2019 10:59, nathalie ramat wrote: >>> ???????????? Checking file: /etc/samba/smb.conf >>> >>> # Global parameters >>> [global] >>> ?????? dns forwarder = 192.168.xx.230 >> You cannot forward to the DC itself, it
2019 Oct 23
2
net ads join -- strange message
Hello, I have an server ad? - everything seems ok I have a windows client and a linux client . The users must to connect on windows or on linux with the same home. when I join my client linux with the command net ads join -U administration I have after the following message net ads join -U administrator Enter administrator's password: Error reading password from file descriptor 0: empty
2019 Oct 16
0
message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
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 [SAMBADOM]: > Server Role (dc, member, standalone) [dc]:? dc > DNS backend (SAMBA_INTERNAL,
2019 Oct 25
1
net ads join -- strange message
hello, Le 23/10/2019 ? 12:45, Rowland penny via samba a ?crit?: > On 23/10/2019 10:51, nathalie ramat via samba wrote: >> Hello, >> >> I have an server ad? - everything seems ok >> I have a windows client and a linux client . The users must to >> connect on windows or on linux with the same home. >> >> when I join my client linux with the command net
2019 Nov 07
2
net ads join explication ?
My Dc is under linux - my version of linux is 5.2.0-3-amd64 My client os is also under linux et the version is 5.2.0-2-amd64. I have also client windows10. I put the result of the test Collected config? --- 2019-11-07-13:14 ----------- Hostname: clientblues2 DNS Domain: sambadom.calais.fr FQDN: clientblues2.sambadom.calais.fr ipaddress: 192.168.xx.233 ----------- Kerberos SRV
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
2016 Jun 05
2
inconsistent DNS information, windows domain member issues..
I joined a Windows 10 Pro system to my (still experimental) domain. The windows system actually hosts DC2 as a VM, and another Windows (Server 2008 R2) at another location hosts DC1 also as a VM. The two locations are connected via a VPN, both systems run only when needed. The windows system does not directly use DC2 for DNS but instead talks to a DNS resolver that delegates the samba Domain to
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:
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
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
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
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
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) >
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 Nov 07
0
net ads join explication ?
In addition to Rowland's comment. What i dont get here. Your running Debian Bullseye. (i hope not in production) You didnt update it. ( samba 4.9.13 is set and not the current one for bullseye (samba 4.11.1-2) Bullseye = testing, and believe me, testing has more problems then unstable.. So would start with running : apt-get dist-upgrade Then you configs, these dont look bad, but you
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
2019 Nov 07
1
net ads join explication ?
Hello , I want to add my linux client in my ad . I use net ads join -U administrator passwd : xxxx and I wait and I have no reponse but if I put 8 times t he key enter,? my machine is add to my add but I have? this message error : error reading from file descriptor 0 : empty password? which come from the server I don't understand why . My server is samba 4.11 and? my client use winbind