SQL5043N  Support for one or more communications protocols failed to start
successfully. However, core database manager functionality started successfully.

D:ProgramsIBMWebSphereAppServerdb2BIN>db2 connect to QECMNDB
SQL30081N  A communication error has been detected. Communication protocol
being used: "TCP/IP".  Communication API being used: "SOCKETS".  Location
where the error was detected: "192.168.2.100".  Communication function
detecting the error: "connect".  Protocol specific error code(s): "10061", "*",
"*".  SQLSTATE=08001

>db2set -all
[e] DB2PATH=D:ProgramsIBMWebSphereAppServerdb2
[i] DB2INSTPROF=C:ProgramDataIBMDB2DB2COPY1
[i] DB2COMM=TCPIP
[g] DB2_CREATE_DB_ON_PATH=YES
[g] DB2_EXTSECURITY=YES
[g] DB2_GRP_LOOKUP=LOCAL,TOKENLOCAL
[g] DB2SYSTEM=MYNOTEBOOK1
[g] DB2PATH=D:ProgramsIBMWebSphereAppServerdb2
[g] DB2INSTDEF=BPMINST
[g] DB2ADMINSERVER=DB2DAS00

db2c_BPMINST    50000/tcp

2013-10-10-23.49.14.054000+120 I1470074F426       LEVEL: Event
PID     : 7648                 TID  : 6648        PROC : db2syscs.exe
INSTANCE: BPMINST              NODE : 000
EDUID   : 6648                 EDUNAME: db2sysc
FUNCTION: DB2 UDB, fast comm manager, sqlkf_init_allocate_shared, probe:500
START   : FCM infrastructure started
FCM running in non-shared mode; FCM parallelism degree: 1; comm protocol: TCP/IPv4

2013-10-10-23.49.16.132000+120 I1470502F365       LEVEL: Error
PID     : 7648                 TID  : 6648        PROC : db2syscs.exe
INSTANCE: BPMINST              NODE : 000
EDUID   : 6648                 EDUNAME: db2sysc
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr, probe:47
MESSAGE : DIA3202C The TCP/IP call "bind" returned an errno="10013".