slow initial Domain Controller communication after adding machine to another domain

[Ilya Basin]

Hi Andrey.
No I didn't enable cygserver. There's another issue: if I try to list a directory where files are owned by a domain user of the old domain then the delay is the number of files multiplied by a few seconds. So tools like rsync are very slow. I think we need a cache for failed user id mappings.


-------- Original Message --------
From: Andrey Repin <anrdaemon@yandex.ru>
Sent: Friday, November 14, 2025 at 11:55 AM UTC+3
To: Ilya Basin <basinilya@gmail.com>, cygwin@cygwin.com
Subject: RE: slow initial Domain Controller communication after adding machine to another domain

Greetings, Ilya Basin!

>> Hi List.
>> Be it /bin/bash.exe or even /bin/echo.exe, when I launch this program from Windows it takes 15 seconds to start.
>> procmon shows that it communicates with our domain controller port 389 (ldap) during this time.

>> I tried to completely recreate /etc/group and /etc/passwd and I tried to
>> delete them. It didn't make any difference.
>> However, mkpasswd and mkgroup themselves complete instantly.

>> Querying the Active Directory with a powershel cmdlet is fast (the port is different though: 9389).

Do you have a cygserver running?