Question & Answer
When connecting from a DB2 Windows client with an ID which does not exist in the Windows client or the Windows client’s domain, the connection may take a long time.
By default, a DB2 Windows client would authenticate an ID. If the ID does not exist, the domain will be queried and also its trusted domains. It could take a long time query all trusted domains.
Cataloging database as authentication set to server stops DB2 Windows client to authenticate. The following is the command to catalog a database as authentication set to server.
db2 catalog db <database name> at node <node name> authentication server
16 June 2018