DJoin cannot find domain controllers

Questions about WAPT Server / Requests and help related to the WAPT server
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
Answer
AdamBertok
Messages: 1
Registration: Sep 7, 2026 - 3:09 p.m.

September 8, 2026 - 9:34 AM

Dear Tranquil IT team,

Apologies in advance for the English-language post.

I would like to ask whether anyone else has run into the following issue. I believe this may be a potential bug currently present in the WAPT console.

The symptom is as follows:
When preparing a machine with djoin under the OS Deploy tab, we get the error message "Cannot find any domain controllers for<domain> "
djoin.png
djoin.png (12.65 KB) Viewed 246 times
I suspect this may be related to the most recent Samba update.
BUG 15988: Samba internal DNS service doesn't handle switch from UDP to TCP when packet is larger than 4k
https://bugzilla.samba.org/show_bug.cgi?id=15988

According to the bug, Samba's internal DNS service redirects any UDP packet larger than 512 bytes to the TCP protocol.

Evidence:
Every time, I try to refresh and get domain controllers we the following traffic happen in the background.
wireshark.png
wireshark.png (3.03 KB) Viewed 246 times
WAPT console try to request _ldap._tcp.<domain> .
Samba internal dns response with the same payload indicating the TC flag, which should trigger TCP request from client side, but that request never happen.
In our case, the DNS response to this packet is larger than 512 bytes.
wireshark-tc.png
wireshark-tc.png (7.11 KB) Viewed 246 times
The nslookup _ldap._tcp.<domain> from windows or command line just working fine.

Environment:
Samba:
- Debian 13 Trixie
- Samba Version: Sernet 4.24.6-4

WAPT:
- Debian 13 Trixie
- WAPT version: 2.6.1.17765

This issue is currently affecting several of our WAPT servers. Has anyone else run into this problem as well?

Thank you in advance!
High
Answer

Return to "WAPT Server"


  • To go further with WAPT