Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: DRDA Client cannot connect to DB2 for z/OS via IBM DB2 Connect gateway when configured for encrypted authentication


View products that this article applies to.

Symptoms

DRDA client supporting the DB2 connector within Excel cannot connect to DB2 for z/OS through an intermediary IBM DB2 Connect gateway when gateway is configured for encrypted authentication by using Advanced Encryption Standard (AES) instead of Data Encryption Standard (DES), returning an authentication failure error.

↑ Back to the top


Cause

DRDA Client cannot determine correct encryption algorithm at connect time. Use ADO.NET provider for DRDA (DrdaClient) or ADO.NET provider for DB2 (MsDb2Client) connection string argument EncryptionAlgorithm=AES to instruct DRDA Client to utilize DRDA Encryption Algorithm (ENCALG) Advanced Encryption Standard (AES) on DRDA Security Mechanism (SECMEC) when processing DRDA Security Check (SECCHK).

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

↑ Back to the top


Resolution

This issue is fixed in the following cumulative update for Host Integration Server:

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products

↑ Back to the top


Keywords: CI122143, kbHotfixAuto, kbqfe, kbfix, kb

↑ Back to the top

Article Info
Article ID : 4559735
Revision : 4
Created on : 8/24/2020
Published on : 8/24/2020
Exists online : False
Views : 213