Hi,

I tracked down our problems with Remote Loader crashing the Domain
Controller e.g. RPC / Replication. It seems to be caused by thousands of
"CLOSE_WAIT" connections of the Remote Loader e.g. (dumped with "netstat
-an" on a Windows 2003 SP1 Domain Controller running IDM 3 Remote Loader):

TCP 127.0.0.1:1037 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1039 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1040 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1041 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1042 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1043 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1044 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1045 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1046 127.0.0.1:389 CLOSE_WAIT
TCP 127.0.0.1:1047 127.0.0.1:389 CLOSE_WAIT

....after some time I get ~4000 connections in "CLOSE_WAIT" state - like
above - some TIME_WAIT some ESTABLISHED, too. By this time Active
Directory is inaccessible (e.g. via MMC), RPC service is down. By
stopping the Remote Loader Service / Process from its console and
starting it again, the CLOSE_WAIT sockets disapear and the domain
controller (MMC, RPC, replication) works fine again.

Seems like a bug likely in ADDriver.dll to me?! We use version:

ADDriver.dll 675.840 Bytes (no version in file - but regular IDM 3)
dirxml.dlm 3.0.0.62638

Sebastian Rieger