search for: nafs39h19ie

...2022 lab and 2025 lab): (Note that due to the identical lab setup, the DC hostname is the same. **These machines are in isolated networks and cannot see eachother**.) -- 8< snip -- root at dom-test-member:~# wbinfo --ping-dc checking the NETLOGON for domain[DOMTEST] dc connection to "WIN-NAFS39H19IE.domtest.howett.net" succeeded root at dom-test-member:~# wbinfo -u DOMTEST\administrator DOMTEST\guest DOMTEST\krbtgt DOMTEST\dustin root at dom-test-member:~# --- root at dom2-test-member:~# wbinfo --ping-dc checking the NETLOGON for domain[DOMTEST] dc connection to "WIN-NAFS39H19IE.d...

...OMTEST: NetrGetAnyDCName: domtest: No such trusted domain ... which matches up with a log entry in log.winbindd-DOMTEST + [2025/04/24 01:00:39.489494, 10, pid=694, effective(0, 0), real(0, 0), class=rpc_cli] ../../source3/rpc_client/cli_pipe.c:1028(rpc_api_pipe_got_pdu) + rpc_api_pipe: host WIN-NAFS39H19IE.domtest.howett.net returned 8 bytes. + [2025/04/24 01:00:39.489502, 1, pid=694, effective(0, 0), real(0, 0), class=rpc_parse] ../../librpc/ndr/ndr.c:490(ndr_print_function_debug) + netr_GetAnyDCName: struct netr_GetAnyDCName + out: struct netr_GetAnyDCName + dcname...