Hello,
when I install WAPT server on a Debian 9 machine, I have no problems until I try to configure Kerberos.
The "kinit" command always returns the following error:
Cannot contact any KDC for realm 'MONDOMAINE.LOCAL' while getting initial credentials
. The server name is correctly resolved at the DNS level.
The AD server (and Kerberos) is running Windows Server 2016.
The WAPT version is 1.5.23.
[SOLVED] Kerberos configuration issue
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Nicoge,
The problem with .local comes from the Bonjour/MDNS protocol (multicast DNS). One day, a few years ago, Apple decreed that the .local suffix would correspond to DNS names resolvable via multicast (a bit like NetBIOS broadcast) with its Bonjour protocol.
So now we can no longer use this suffix unless we disable mdns, and that's that. On most Linux distributions, mdns is now configured by default (see the /etc/nsswitch.conf file). On Windows, it's enabled when you install certain programs like Adobe Photoshop. On Macs, it's always installed.
So basically, if you have a new domain to set up, don't use the .local suffix.
Denis
It can work with a .LOCAL.
The problem with .local comes from the Bonjour/MDNS protocol (multicast DNS). One day, a few years ago, Apple decreed that the .local suffix would correspond to DNS names resolvable via multicast (a bit like NetBIOS broadcast) with its Bonjour protocol.
So now we can no longer use this suffix unless we disable mdns, and that's that. On most Linux distributions, mdns is now configured by default (see the /etc/nsswitch.conf file). On Windows, it's enabled when you install certain programs like Adobe Photoshop. On Macs, it's always installed.
So basically, if you have a new domain to set up, don't use the .local suffix.
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
