Ich habe meinen letztjährigen Debian12-Client virtuell gepflegt, habe dazu eine Maschine im Proxmox, auf die ich von zu Hause aus zugreifen kann.
Das wollte ich nun mit meinem diesjährigen Debian 13 Client auch so machen - ich bekomme aber keine Domänenanmeldung.
Mit „echten“ Maschinen funktioniert der Client, er lässt sich auch clonen. Ich bin ratlos.
Folgendes sind die Fehlermeldungen, die ich bekomme (auszugsweise, ich hoffe, ich habe eine sinnvolle Auswahl getroffen)
nmbd[782]: query_name_response: Multiple (2) responses received for a query on subnet 10.0.0.31 for name WORKGROUP<1d>.
Aug 04 19:04:29 M1984 systemd[1]: Starting winbind.service - Samba Winbind Daemon...
Aug 04 19:04:29 M1984 nmbd[782]: This response was from IP 10.0.0.28, reporting an IP address of 10.0.0.28.
kernel: CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed
Aug 04 19:04:33 M1984 kernel: CIFS: VFS: \\server.ohg-netz.llan Send error in SessSetup = -126
Aug 04 19:04:33 M1984 kernel: CIFS: VFS: cifs_mount failed w/return code = -126
onBoot[775]: * Error mounting share //server.ohg-netz.llan/sysvol to /srv/samba/M1984$/sysvol!
Aug 04 19:04:33 M1984 linuxmuster-linuxclient7[866]: [FATAL] (shares) * Error mounting share //server.ohg-netz.llan/sysvol to /srv/samba/M1984$/sysvol!
Aug 04 19:04:33 M1984 linuxmuster-linuxclient7[867]: [INFO] (hooks) === Running local hook onBoot in /etc/linuxmuster-linuxclient7/onBoot.d ===
Aug 04 19:04:34 M1984 onBoot[868]: id: ‘M1984$’: Einen solchen Benutzer gibt es nicht
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[869]: [WARNING] (localUserHelper) Exception when querying groups of user M1984$, it probably does not exist
Aug 04 19:04:34 M1984 onBoot[870]: id: ‘M1984$’: Einen solchen Benutzer gibt es nicht
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[871]: [WARNING] (localUserHelper) Exception when querying groups of user M1984$, it probably does not exist
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[872]: [ERROR] (ldapHelper) Cloud not bind to ldap!
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[873]: [ERROR] (ldapHelper) === An exception occurred ===
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[874]: [ERROR] (ldapHelper) {'result': -2, 'desc': 'Local error', 'ctrls': [], 'info': 'SASL(-1): generic fai>
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[875]: [ERROR] (ldapHelper) === end exception ===
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[876]: [ERROR] (ldapHelper) Cannot talk to LDAP
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[877]: [INFO] (hooks) == Executing script /etc/linuxmuster-linuxclient7/onBoot.d/00_example.sh ==
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[886]: [INFO] (hooks) ==> Script /etc/linuxmuster-linuxclient7/onBoot.d/00_example.sh finished with exit code>
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[887]: [INFO] (hooks) ===> Finished running local hook onBoot ===
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[888]: [INFO] (hooks) === Running remote hook onBoot ===
Aug 04 19:04:34 M1984 onBoot[889]: id: ‘M1984$’: Einen solchen Benutzer gibt es nicht
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[890]: [WARNING] (localUserHelper) Exception when querying groups of user M1984$, it probably does not exist
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[891]: [ERROR] (ldapHelper) Cloud not bind to ldap!
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[892]: [ERROR] (ldapHelper) === An exception occurred ===
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[893]: [ERROR] (ldapHelper) {'result': -2, 'desc': 'Local error', 'ctrls': [], 'info': 'SASL(-1): generic fai>
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[894]: [ERROR] (ldapHelper) === end exception ===
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[895]: [ERROR] (ldapHelper) Cannot talk to LDAP
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[896]: [ERROR] (hooks) Could not execute server hooks because the computer config could not be read
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[897]: [INFO] (hooks) ===> Finished running remote hook onBoot ===
Aug 04 19:04:34 M1984 linuxmuster-linuxclient7[898]: [INFO] (__main__) ======> onBoot end ======
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (__main__) ====== onBoot started ======
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (keytab) Patching /etc/krb5.keytab
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749$ was changed to M1984$
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749$ was changed to M1984$
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749$ was changed to M1984$
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749 was changed to M1984
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749 was changed to M1984
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749 was changed to M1984
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) m749.ohg-netz.llan was changed to m1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) m749.ohg-netz.llan was changed to m1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) m749.ohg-netz.llan was changed to m1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749.ohg-netz.llan was changed to M1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749.ohg-netz.llan was changed to M1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) M749.ohg-netz.llan was changed to M1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) m749.ohg-netz.llan was changed to m1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) m749.ohg-netz.llan was changed to m1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (keytab) m749.ohg-netz.llan was changed to m1984.ohg-netz.llan
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (keytab) Trying to overwrite /etc/krb5.keytab
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (shares) Calculating mountpoint of //server.ohg-netz.llan/sysvol
Aug 04 19:04:34 M1984 onBoot[775]: [WARNING] (shares) Uid could not be found! Continuing anyway!
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (shares) Trying to mount '//server.ohg-netz.llan/sysvol' to '/srv/samba/M1984$/sysvol'
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (shares) * Creating directory...
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (shares) * Executing '/usr/sbin/mount.cifs -o file_mode=0700,dir_mode=0700,sec=krb5,nodev,nosuid,mfsymlinks,nobr>
Aug 04 19:04:34 M1984 onBoot[775]: [DEBUG] (shares) * Trying to mount...
Aug 04 19:04:34 M1984 onBoot[775]: [FATAL] (shares) * Error mounting share //server.ohg-netz.llan/sysvol to /srv/samba/M1984$/sysvol!
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (hooks) === Running local hook onBoot in /etc/linuxmuster-linuxclient7/onBoot.d ===
Aug 04 19:04:34 M1984 onBoot[775]: [WARNING] (localUserHelper) Exception when querying groups of user M1984$, it probably does not exist
Aug 04 19:04:34 M1984 onBoot[775]: [WARNING] (localUserHelper) Exception when querying groups of user M1984$, it probably does not exist
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) Cloud not bind to ldap!
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) === An exception occurred ===
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) Cannot talk to LDAP
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (hooks) == Executing script /etc/linuxmuster-linuxclient7/onBoot.d/00_example.sh ==
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (hooks) ==> Script /etc/linuxmuster-linuxclient7/onBoot.d/00_example.sh finished with exit code 0 ==
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (hooks) ===> Finished running local hook onBoot ===
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (hooks) === Running remote hook onBoot ===
Aug 04 19:04:34 M1984 onBoot[775]: [WARNING] (localUserHelper) Exception when querying groups of user M1984$, it probably does not exist
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) Cloud not bind to ldap!
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) === An exception occurred ===
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) {'result': -2, 'desc': 'Local error', 'ctrls': [], 'info': 'SASL(-1): generic failure: GSSAPI Error>
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) === end exception ===
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (ldapHelper) Cannot talk to LDAP
Aug 04 19:04:34 M1984 onBoot[775]: [ERROR] (hooks) Could not execute server hooks because the computer config could not be read
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (hooks) ===> Finished running remote hook onBoot ===
Aug 04 19:04:34 M1984 onBoot[775]: [INFO] (__main__) ======> onBoot end ======
Aug 04 19:04:34 M1984 systemd[1]: Finished linuxmuster-linuxclient7.service - linuxmuster: switch local and remote home depending on ad server connection.
Aug 04 19:04:34 M1984 systemd[1]: Starting sssd.service - System Security Services Daemon...
Aug 04 19:04:37 M1984 sssd[911]: Starting up
Aug 04 19:04:38 M1984 sssd_be[913]: Starting up
Aug 04 19:04:38 M1984 sssd_be[913]: PAC check is requested but krb5_validate is set to false. PAC checks will be skipped.
Aug 04 19:04:38 M1984 sssd_nss[915]: Starting up
Aug 04 19:04:38 M1984 sssd_pam[916]: Starting up
Aug 04 19:04:38 M1984 sssd_pac[917]: Starting up
Aug 04 19:04:38 M1984 ldap_child[918]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Client 'M1984$@OHG-NETZ.LLAN' not found in >
Aug 04 19:04:38 M1984 systemd[1]: Started sssd.service - System Security Services Daemon.
Aug 04 19:04:38 M1984 systemd[1]: Reached target nss-user-lookup.target - User and Group Name Lookups.
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-nss.socket - SSSD NSS Service responder socket...
Aug 04 19:04:38 M1984 systemd[1]: Starting accounts-daemon.service - Accounts Service...
Aug 04 19:04:38 M1984 systemd[1]: Started cron.service - Regular background program processing daemon.
Aug 04 19:04:38 M1984 systemd[1]: Starting cups.service - CUPS Scheduler...
Aug 04 19:04:38 M1984 systemd[1]: Starting systemd-logind.service - User Login Management...
Aug 04 19:04:38 M1984 systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions...
Aug 04 19:04:38 M1984 cron[921]: (CRON) INFO (pidfile fd = 3)
Aug 04 19:04:38 M1984 systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions.
Aug 04 19:04:38 M1984 systemd[1]: Starting plymouth-quit-wait.service - Hold until boot process finishes up...
Aug 04 19:04:38 M1984 systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen...
Aug 04 19:04:38 M1984 sssd_check_socket_activated_responders[919]: Misconfiguration found for the 'nss' responder.
It has been configured to be socket-activated but it's still mentioned in the services' >
Please consider either adjusting services' line or disabling the socket by calling:
"systemctl disable sssd-nss.socket"
Aug 04 19:04:38 M1984 systemd[1]: Received SIGRTMIN+21 from PID 257 (plymouthd).
Aug 04 19:04:38 M1984 systemd[1]: Finished plymouth-quit-wait.service - Hold until boot process finishes up.
Aug 04 19:04:38 M1984 systemd[1]: sssd-nss.socket: Failed with result 'exit-code'.
Aug 04 19:04:38 M1984 systemd[1]: Failed to listen on sssd-nss.socket - SSSD NSS Service responder socket.
Aug 04 19:04:38 M1984 systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen.
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-autofs.socket - SSSD AutoFS Service responder socket...
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-pac.socket - SSSD PAC Service responder socket...
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-pam.socket - SSSD PAM Service responder socket...
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-ssh.socket - SSSD SSH Service responder socket...
Aug 04 19:04:38 M1984 cron[921]: (CRON) INFO (Running @reboot jobs)
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-sudo.socket - SSSD Sudo Service responder socket...
Aug 04 19:04:39 M1984 systemd-logind[924]: New seat seat0.
Aug 04 19:04:39 M1984 systemd-logind[924]: Watching system buttons on /dev/input/event1 (Power Button)
Aug 04 19:04:39 M1984 systemd-logind[924]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
Aug 04 19:04:39 M1984 systemd[1]: Started systemd-logind.service - User Login Management.
Aug 04 19:04:39 M1984 systemd[1]: Started veyon.service - Veyon Service.
Aug 04 19:04:39 M1984 kernel: kauditd_printk_skb: 111 callbacks suppressed
Aug 04 19:04:39 M1984 kernel: audit: type=1400 audit(1785863079.124:123): apparmor="DENIED" operation="open" class="file" profile="/usr/sbin/cupsd" name="/>
Aug 04 19:04:39 M1984 systemd[1]: Listening on sssd-autofs.socket - SSSD AutoFS Service responder socket.
Aug 04 19:04:39 M1984 sssd_check_socket_activated_responders[940]: Misconfiguration found for the 'pam' responder.
It has been configured to be socket-activated but it's still mentioned in the services' >
Please consider either adjusting services' line or disabling the socket by calling:
"systemctl disable sssd-pam.socket"
Aug 04 19:04:39 M1984 systemd[1]: sssd-pam.socket: Control process exited, code=exited, status=17/n/a
Aug 04 19:04:39 M1984 systemd[1]: sssd-pam.socket: Failed with result 'exit-code'.
Aug 04 19:04:39 M1984 systemd[1]: Failed to listen on sssd-pam.socket - SSSD PAM Service responder socket.
Aug 04 19:04:39 M1984 sssd_check_socket_activated_responders[939]: Misconfiguration found for the 'pac' responder.
It has been configured to be socket-activated but it's still mentioned in the services' >
Please consider either adjusting services' line or disabling the socket by calling:
"systemctl disable sssd-pac.socket"
Aug 04 19:04:39 M1984 systemd[1]: sssd-pac.socket: Control process exited, code=exited, status=17/n/a
Aug 04 19:04:39 M1984 systemd[1]: sssd-pac.socket: Failed with result 'exit-code'.
Aug 04 19:04:39 M1984 systemd[1]: Failed to listen on sssd-pac.socket - SSSD PAC Service responder socket.
Aug 04 19:04:39 M1984 systemd[1]: Listening on sssd-sudo.socket - SSSD Sudo Service responder socket.
Aug 04 19:04:39 M1984 systemd[1]: Listening on sssd-ssh.socket - SSSD SSH Service responder socket.
Aug 04 19:04:39 M1984 ldap_child[957]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Client 'M1984$@OHG-NETZ.LLAN' not found in >
Aug 04 19:04:39 M1984 accounts-daemon[920]: started daemon version 23.13.9
Aug 04 19:04:39 M1984 systemd[1]: Started accounts-daemon.service - Accounts Service.
Aug 04 19:04:40 M1984 dbus-daemon[663]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1>
Aug 04 19:04:40 M1984 systemd[1]: Starting colord.service - Manage, Install and Generate Color Profiles...
Aug 04 19:04:41 M1984 dbus-daemon[663]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Aug 04 19:04:41 M1984 systemd[1]: Started colord.service - Manage, Install and Generate Color Profiles.
Aug 04 19:04:41 M1984 ldap_child[966]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Client 'M1984$@OHG-NETZ.LLAN' not found in >
Aug 04 19:04:44 M1984 systemd[1]: Started cups.service - CUPS Scheduler.
Aug 04 19:04:44 M1984 kernel: audit: type=1400 audit(1785863084.060:124): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=9>
Aug 04 19:04:44 M1984 systemd[1]: Started cups-browsed.service - Make remote CUPS printers available locally.
Aug 04 19:04:38 M1984 systemd[1]: sssd-nss.socket: Failed with result 'exit-code'.
Aug 04 19:04:38 M1984 systemd[1]: Failed to listen on sssd-nss.socket - SSSD NSS Service responder socket.
Aug 04 19:04:38 M1984 systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen.
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-autofs.socket - SSSD AutoFS Service responder socket...
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-pac.socket - SSSD PAC Service responder socket...
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-pam.socket - SSSD PAM Service responder socket...
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-ssh.socket - SSSD SSH Service responder socket...
Aug 04 19:04:38 M1984 cron[921]: (CRON) INFO (Running @reboot jobs)
Aug 04 19:04:38 M1984 systemd[1]: Starting sssd-sudo.socket - SSSD Sudo Service responder socket...
Aug 04 19:04:39 M1984 systemd-logind[924]: New seat seat0.
Aug 04 19:04:39 M1984 systemd-logind[924]: Watching system buttons on /dev/input/event1 (Power Button)
Aug 04 19:04:39 M1984 systemd-logind[924]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
Aug 04 19:04:39 M1984 systemd[1]: Started systemd-logind.service - User Login Management.
Aug 04 19:04:39 M1984 systemd[1]: Started veyon.service - Veyon Service.
Aug 04 19:04:39 M1984 kernel: kauditd_printk_skb: 111 callbacks suppressed
Aug 04 19:04:39 M1984 kernel: audit: type=1400 audit(1785863079.124:123): apparmor="DENIED" operation="open" class="file" profile="/usr/sbin/cupsd" name="/>
Aug 04 19:04:39 M1984 systemd[1]: Listening on sssd-autofs.socket - SSSD AutoFS Service responder socket.
Aug 04 19:04:39 M1984 sssd_check_socket_activated_responders[940]: Misconfiguration found for the 'pam' responder.
It has been configured to be socket-activated but it's still mentioned in the services' >
Please consider either adjusting services' line or disabling the socket by calling:
"systemctl disable sssd-pam.socket"
Aug 04 19:04:39 M1984 systemd[1]: sssd-pam.socket: Control process exited, code=exited, status=17/n/a
Aug 04 19:04:39 M1984 systemd[1]: sssd-pam.socket: Failed with result 'exit-code'.
Aug 04 19:04:39 M1984 systemd[1]: Failed to listen on sssd-pam.socket - SSSD PAM Service responder socket.
Aug 04 19:04:39 M1984 sssd_check_socket_activated_responders[939]: Misconfiguration found for the 'pac' responder.
It has been configured to be socket-activated but it's still mentioned in the services' >
Please consider either adjusting services' line or disabling the socket by calling:
"systemctl disable sssd-pac.socket"
Aug 04 19:04:39 M1984 systemd[1]: sssd-pac.socket: Control process exited, code=exited, status=17/n/a
Aug 04 19:04:39 M1984 systemd[1]: sssd-pac.socket: Failed with result 'exit-code'.
Aug 04 19:04:39 M1984 systemd[1]: Failed to listen on sssd-pac.socket - SSSD PAC Service responder socket.
Aug 04 19:04:39 M1984 systemd[1]: Listening on sssd-sudo.socket - SSSD Sudo Service responder socket.
Aug 04 19:04:39 M1984 systemd[1]: Listening on sssd-ssh.socket - SSSD SSH Service responder socket.
Aug 04 19:04:39 M1984 ldap_child[957]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Client 'M1984$@OHG-NETZ.LLAN' not found in >
Aug 04 19:04:39 M1984 accounts-daemon[920]: started daemon version 23.13.9
Aug 04 19:04:39 M1984 systemd[1]: Started accounts-daemon.service - Accounts Service.
Aug 04 19:04:40 M1984 dbus-daemon[663]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1>
Aug 04 19:04:40 M1984 systemd[1]: Starting colord.service - Manage, Install and Generate Color Profiles...
Aug 04 19:04:41 M1984 dbus-daemon[663]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Aug 04 19:04:41 M1984 systemd[1]: Started colord.service - Manage, Install and Generate Color Profiles.
Aug 04 19:04:41 M1984 ldap_child[966]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Client 'M1984$@OHG-NETZ.LLAN' not found in >
Aug 04 19:04:44 M1984 systemd[1]: Started cups.service - CUPS Scheduler.
Aug 04 19:04:44 M1984 kernel: audit: type=1400 audit(1785863084.060:124): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=9>
Aug 04 19:04:44 M1984 systemd[1]: Started cups-browsed.service - Make remote CUPS printers available locally.
ug 04 19:06:54 M1984 ldap_child[1137]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Client 'M1984$@OHG-NETZ.LLAN' not found in>
Aug 04 19:06:56 M1984 ldap_child[1138]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Client 'M1984$@OHG-NETZ.LLAN' not found in>
Aug 04 19:07:00 M1984 s
Der Client sollte die IP 10.0.0.31 haben, hat er im Linbo auch.
Der Client, von dem ich diesen ursprünglich kopiert hatte, hat die 10.0.0.28 (die ja am Anfang in einer Fehlermeldung auch auftaucht) - die MAC der virtuellen Netzwerkkarte habe ich aber natürlich geändert!
Ich verstehe so viel, dass der Maschinenaccount (der Client heißt M1984) nicht existiert / nicht funktioniert, deswegen Kerberos nicht funktioniert und man sich deswegen nicht anmelden kann und CIFS auch die Share nicht mountet. Ich habe aber keinerlei Idee, woran das noch liegen könnte.
Habt Ihr Ideen?
Gruß, Andreas