DB2 Connect v7.2 on Windows platform...

Error message:
2004-08-14-21.18.23.800001 Instance:DB2 Node:000
PID:2584(namgr.EXE) TID:2580 Appid:092D72E5.8E0F.040814085003
common_communication sqlcctcpconnr Probe:101
DIA3202C The TCP/IP call "connect" returned an errno="10060".

I found this errno="10060" to mean:
WSAETIMEDOUT (10060): The establishment of a connection timed out before a connection was made.

All we're doing is having notes applications use DB2 ODBC to connect to other defined datasources. This is failing intermittently, then starts to fail more and more often with the above error message in the DB2DIAG log appearing often. We've already tried a reinstall of DB2 Connect. Do I increase the timeout somewhere or is there another problem at hand ? This started happening for no apparent reason a few weeks back.

Weird thing is that connects made from Command Center or CLP are always successful.

Actually, this looks like a network problem to me...

I should also add that a reboot of the box clears this "snowball effect" of more and more failures.. but it does eventually build up in number again. Does that still say network issue to you ? Or perhaps memory leak ? Can this symptom still be DB2-related ?

I don't have any experience with DB2 Connect on Windows but I read the log messages as this:
- DB2 Connect requests a network connection to the host
- WinSock, Windows socket driver returns an error because of a timeout
- the error gets reported in the db2diag.log

I'd first make sure that the Windows TCP/IP stack is patched up to date and monitor network performance at the time when those errors occur: check how fast your DNS server responds; if you can ping the host at all; run a tracert and see the delays.