nathalie ramat
2019-Oct-16 09:59 UTC
[Samba] 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 >> 192.168.xx.230?????? blueyestest.sambadom.calais.fr >> sambadom.calais.fr blueyestest > > You should only have the domain once i.e. > > 192.168.xx.230 blueyestest.sambadom.calais.fr blueyetest >ok ->> >> # The following lines are desirable for IPv6 capable hosts >> ::1???????? localhost ip6-localhost ip6-loopback >> ff02::1 ip6-allnodes >> ff02::2 ip6-allrouters >> >> ----------- >> >> ?????? Warning,?? does not exist >> >> ----------- > > And there is the catastrophic bit. you do not seem to have a smb.conf > file. > > Rowland > > > > >my smb.conf is locate at /etc/samba I put the new trace Collected config? --- 2019-10-16-11:48 ----------- Hostname: blueyestest DNS Domain: sambadom.calais.fr FQDN: blueyestest.sambadom.calais.fr ipaddress: 192.168.xx.230 ----------- Kerberos SRV _kerberos._tcp.sambadom.calais.fr record verified ok, sample output: Server:??? ??? 192.168.xx.230 Address:??? 192.168.xx.230#53 _kerberos._tcp.sambadom.calais.fr??? service = 0 100 88 blueyestest.sambadom.calais.fr. Samba is running as an AD DC ----------- ?????? Checking file: /etc/os-release PRETTY_NAME="Debian GNU/Linux bullseye/sid" NAME="Debian GNU/Linux" ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" ----------- This computer is running Debian bullseye/sid x86_64 ----------- running command : ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 ??? link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 ??? inet 127.0.0.1/8 scope host lo ??? inet6 ::1/128 scope host 2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ??? link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff ??? inet 192.168.xx.230/24 brd 192.168.22.255 scope global ens18 ----------- ?????? Checking file: /etc/hosts 127.0.0.1??? localhost 192.168.xx.230??? blueyestest.sambadom.calais.fr blueyestest # The following lines are desirable for IPv6 capable hosts ::1???? localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters ----------- ?????? Checking file: /etc/resolv.conf nameserver 192.168.xx.230 nameserver xxx.xx.xxx.xx ----------- ?????? Checking file: /etc/krb5.conf [libdefaults] ??? default_realm = SAMBADOM.CALAIS.FR ??? dns_lookup_realm = false ??? dns_lookup_kdc = true # The following krb5.conf variables are only for MIT Kerberos. ??? kdc_timesync = 1 ??? ccache_type = 4 ??? forwardable = true ??? proxiable = true # The following encryption type specification will be used by MIT Kerberos # if uncommented.? In general, the defaults in the MIT Kerberos code are # correct and overriding these specifications only serves to disable new # encryption types as they are added, creating interoperability problems. # # The only time when you might need to uncomment these lines and change # the enctypes is if you have local software that will break on ticket # caches containing ticket encryption types it doesn't know about (such as # old versions of Sun Java). #??? default_tgs_enctypes = des3-hmac-sha1 #??? default_tkt_enctypes = des3-hmac-sha1 #??? permitted_enctypes = des3-hmac-sha1 # The following libdefaults parameters are only for Heimdal Kerberos. ??? fcc-mit-ticketflags = true [realms] ??? SAMBADOM.CALAIS.FR = { ??? ??? kdc = blueyestest.sambadom.calais.fr ??? ??? admin_server = blueyestest.sambadom.calais.fr ??? } ??? ATHENA.MIT.EDU = { ??? ??? kdc = kerberos.mit.edu ??? ??? kdc = kerberos-1.mit.edu ??? ??? kdc = kerberos-2.mit.edu:88 ??? ??? admin_server = kerberos.mit.edu ??? ??? default_domain = mit.edu ??? } ??? ZONE.MIT.EDU = { ??? ??? kdc = casio.mit.edu ??? ??? kdc = seiko.mit.edu ??? ??? admin_server = casio.mit.edu ??? } ??? CSAIL.MIT.EDU = { ??? ??? admin_server = kerberos.csail.mit.edu ??? ??? default_domain = csail.mit.edu ??? } ??? IHTFP.ORG = { ??? ??? kdc = kerberos.ihtfp.org ??? ??? admin_server = kerberos.ihtfp.org ??? } ??? 1TS.ORG = { ??? ??? kdc = kerberos.1ts.org ??? ??? admin_server = kerberos.1ts.org ??? } ??? ANDREW.CMU.EDU = { ??? ??? admin_server = kerberos.andrew.cmu.edu ??? ??? default_domain = andrew.cmu.edu ??? } ??????? CS.CMU.EDU = { ??????????????? kdc = kerberos-1.srv.cs.cmu.edu ??????????????? kdc = kerberos-2.srv.cs.cmu.edu ??????????????? kdc = kerberos-3.srv.cs.cmu.edu ??????????????? admin_server = kerberos.cs.cmu.edu ??????? } ??? DEMENTIA.ORG = { ??? ??? kdc = kerberos.dementix.org ??? ??? kdc = kerberos2.dementix.org ??? ??? admin_server = kerberos.dementix.org ??? } ??? stanford.edu = { ??? ??? kdc = krb5auth1.stanford.edu ??? ??? kdc = krb5auth2.stanford.edu ??? ??? kdc = krb5auth3.stanford.edu ??? ??? master_kdc = krb5auth1.stanford.edu ??? ??? admin_server = krb5-admin.stanford.edu ??? ??? default_domain = stanford.edu ??? } ??????? UTORONTO.CA = { ??????????????? kdc = kerberos1.utoronto.ca ??????????????? kdc = kerberos2.utoronto.ca ??????????????? kdc = kerberos3.utoronto.ca ??????????????? admin_server = kerberos1.utoronto.ca ??????????????? default_domain = utoronto.ca ??? } [domain_realm] ??? .mit.edu = ATHENA.MIT.EDU ??? mit.edu = ATHENA.MIT.EDU ??? .media.mit.edu = MEDIA-LAB.MIT.EDU ??? media.mit.edu = MEDIA-LAB.MIT.EDU ??? .csail.mit.edu = CSAIL.MIT.EDU ??? csail.mit.edu = CSAIL.MIT.EDU ??? .whoi.edu = ATHENA.MIT.EDU ??? whoi.edu = ATHENA.MIT.EDU ??? .stanford.edu = stanford.edu ??? .slac.stanford.edu = SLAC.STANFORD.EDU ??????? .toronto.edu = UTORONTO.CA ??????? .utoronto.ca = UTORONTO.CA ----------- ?????? Checking file: /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd:???????? files systemd group:????????? files systemd shadow:???????? files gshadow:??????? files hosts:????????? files mdns4_minimal [NOTFOUND=return] dns networks:?????? files protocols:????? db files services:?????? db files ethers:???????? db files rpc:??????????? db files netgroup:?????? nis ----------- ?????? Checking file: /etc/samba/smb.conf # Global parameters [global] ??? dns forwarder = 192.168.xx.230 ??? netbios name = BLUEYESTEST ??? realm = SAMBADOM.CALAIS.FR ??? server role = active directory domain controller ??? workgroup = SAMBADOM ??? idmap_ldb:use rfc2307 = yes ??? log level = 3 ??? log file = /var/log/samba/log.%M [sysvol] ??? path = /var/lib/samba/sysvol ??? read only = No [netlogon] ??? path = /var/lib/samba/sysvol/sambadom.calais.fr/scripts ??? read only = No ----------- *BIND_DLZ not detected in smb.conf --Why i have this message - I choose samba_internal with i used samba-tool domain * ----------- Installed packages: ii? acl 2.2.53-5??????????????????????? amd64??????? access control list - utilities ii? attr 1:2.4.48-5????????????????????? amd64??????? utilities for manipulating filesystem extended attributes ii? fonts-quicksand 0.2016-2??????????????????????? all????????? sans-serif font with round attributes ii? krb5-config 2.6???????????????????????????? all????????? Configuration files for Kerberos Version 5 ii? krb5-locales 1.17-6????????????????????????? all????????? internationalization support for MIT Kerberos ii? krb5-user 1.17-6????????????????????????? amd64??????? basic programs to authenticate using MIT Kerberos ii? libacl1:amd64 2.2.53-5??????????????????????? amd64??????? access control list - shared library ii? libattr1:amd64 1:2.4.48-5????????????????????? amd64??????? extended attribute handling - shared library ii? libgssapi-krb5-2:amd64 1.17-6????????????????????????? amd64??????? MIT Kerberos runtime libraries - krb5 GSS-API Mechanism ii? libkrb5-3:amd64 1.17-6????????????????????????? amd64??????? MIT Kerberos runtime libraries ii? libkrb5support0:amd64 1.17-6????????????????????????? amd64??????? MIT Kerberos runtime libraries - Support library ii? libsmbclient:amd64 2:4.11.0+dfsg-10??????????????? amd64??????? shared library for communication with SMB/CIFS servers ii? libwbclient0:amd64 2:4.11.0+dfsg-10??????????????? amd64??????? Samba winbind client library ii? python-attr 18.2.0-1??????????????????????? all????????? Attributes without boilerplate (Python 2) ii? python3-pyxattr 0.6.1-1???????????????????????? amd64??????? module for manipulating filesystem extended attributes (Python3) ii? python3-samba 2:4.11.0+dfsg-10??????????????? amd64??????? Python 3 bindings for Samba ii? samba 2:4.11.0+dfsg-10??????????????? amd64??????? SMB/CIFS file, print, and login server for Unix ii? samba-common 2:4.11.0+dfsg-10??????????????? all????????? common files used by both the Samba server and client ii? samba-common-bin 2:4.11.0+dfsg-10??????????????? amd64??????? Samba common files used by both the server and the client ii? samba-dsdb-modules:amd64 2:4.11.0+dfsg-10??????????????? amd64??????? Samba Directory Services Database ii? samba-libs:amd64 2:4.11.0+dfsg-10??????????????? amd64??????? Samba core libraries ii? samba-vfs-modules:amd64 2:4.11.0+dfsg-10??????????????? amd64??????? Samba Virtual FileSystem plugins ii? winbind 2:4.11.0+dfsg-10??????????????? amd64??????? service to resolve user and group information from Windows NT servers ----------- -- Nathalie RAMAT-LECLERCQ Service Informatique Universite du Littoral-C?te d'Opale SCoSI - Service Commun du Syst?me d'Information P?le Syst?mes et r?seaux Centre de Gestion Universitaire de Calais 50 rue ferdinand Buisson C.S 80699 62228 CALAIS CEDEX
Rowland penny
2019-Oct-16 10:07 UTC
[Samba] message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
On 16/10/2019 10:59, nathalie ramat wrote:> ?????? Checking file: /etc/samba/smb.conf > > # Global parameters > [global] > ??? dns forwarder = 192.168.xx.230You cannot forward to the DC itself, it needs to be a dns server outside the AD dns domain.> ??? netbios name = BLUEYESTEST > ??? realm = SAMBADOM.CALAIS.FR > ??? server role = active directory domain controller > ??? workgroup = SAMBADOM > ??? idmap_ldb:use rfc2307 = yes > ??? log level = 3 > ??? log file = /var/log/samba/log.%M > > [sysvol] > ??? path = /var/lib/samba/sysvol > ??? read only = No > > [netlogon] > ??? path = /var/lib/samba/sysvol/sambadom.calais.fr/scripts > ??? read only = No > > ----------- > > *BIND_DLZ not detected in smb.conf --Why i have this message - I > choose samba_internal with i used samba-tool domain *You get that message to confirm that smb.conf isn't set up to use Bind9, it is nothing to worry about. The question has to be, why didn't your smb.conf show up the first time ? Rowland
nathalie ramat
2019-Oct-16 10:33 UTC
[Samba] 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 = BLUEYESTEST >> ?????? realm = SAMBADOM.CALAIS.FR >> ?????? server role = active directory domain controller >> ?????? workgroup = SAMBADOM >> ?????? idmap_ldb:use rfc2307 = yes >> ?????? log level = 3 >> ?????? log file = /var/log/samba/log.%M >> >> [sysvol] >> ?????? path = /var/lib/samba/sysvol >> ?????? read only = No >> >> [netlogon] >> ?????? path = /var/lib/samba/sysvol/sambadom.calais.fr/scripts >> ?????? read only = No >> >> ----------- >> >> *BIND_DLZ not detected in smb.conf --Why i have this message - I >> choose samba_internal with i used samba-tool domain * > > You get that message to confirm that smb.conf isn't set up to use > Bind9, it is nothing to worry about. > > The question has to be, why didn't your smb.conf show up the first time ? >I don't know. I restarted the script several times and each time the file smb.conf is present I modified my dns forwarded in my? smb.conf but I have always errors with smbd /usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun fichier ou dossier de ce type /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20756 failed: NT_STATUS_OBJECT_NAME_NOT_FOUND /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20726 failed: NT_STATUS_OBJECT_NAME_NOT_FOUND /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20765 failed: NT_STATUS_OBJECT_NAME_NOT_FOUND /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20750 failed: NT_STATUS_OBJECT_NAME_NOT_FOUND /usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for fde[0x556f777743c0] mpx_fde[(nil)] fd[35] - disabling I saw that this error is always after /usr/sbin/smbd: reloading printcap cache /usr/sbin/smbd: reload status: ok /usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun fichier ou dossier de ce type /usr/sbin/smbd: send_all_fn: messaging_send_buf to 15718 failed: NT_STATUS_OBJECT_NAME_NOT_FOUND /usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for fde[0x55b6941c2c20] mpx_fde[(nil)] fd[35] - disabling I have not configured printers -- Is it a problem ?> Rowland > > >-- Nathalie RAMAT-LECLERCQ Service Informatique Universite du Littoral-C?te d'Opale SCoSI - Service Commun du Syst?me d'Information P?le Syst?mes et r?seaux Centre de Gestion Universitaire de Calais 50 rue ferdinand Buisson C.S 80699 62228 CALAIS CEDEX
Apparently Analagous Threads
- message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
- message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
- message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log
- debian 10: errors with my server samba-ad
- How the program spoolss works ?