RE: Error CPDB053 when accessing Windows server after Windows update

We are current as of January on PTFs.

This is our FTP server that our suppliers, external warehouses, etc. send data to. The IBM I has jobs that processes the data.

We have not disabled SMB2.


Ron Hudson | Programmer / Analyst
+1.704.752.6513 x1324   
www.invue.com
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Friday, July 26, 2019 8:54 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Error CPDB053 when accessing Windows server after Windows update

You're doing FTP to QTNC? That seems odd.

CPE3401 is "Permission denied".

SMB2 is the default on 7.3. Have you disabled it (not recommended)?

Are you current on PTFs?


Thanks



-----Original Message-----
From: Hudson, Ron [mailto:RonHudson@xxxxxxxxx]
Sent: Thursday, July 25, 2019 3:43 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Error CPDB053 when accessing Windows server after Windows update

We have a Windows 2008 R2 server as our FTP server which our IBM I accesses with SQL by /qntc/ServerName/FolderName. This has been working perfectly since 2011.

Last night, a reboot occurred applying the Windows Updates and the IBM I quit accessing the server.
We are receiving error CPDB053 - Error exchanging security information. The error class was 0, and the error code was 3401.
Possible error class and error code values include:
Class 0 - QNTC file system specific security error.
1 - QNTC file system requires digital signing.

We rolled the Windows server back to how it was before, and the IBM I started accessing the server as normal immediately. Therefore, we are out of crisis mode.

Today, we created a new Windows Server 2019 Server. For testing on the new Server 2019, we have all users with full permission. Also, we enabled SMB v1.0 (disabled by default) on the new server, but it was also already enabled on the old one. This new server is getting the same CPDB053 error. I read someone else's post about long share folder names causing problems. On the new server, we have 2 shared folders. Both are named identical to the share names, unless there is an 8 character limit or something. By the way, we are able to connect to these shares via Windows Explorer.

Has anyone encountered this issue before or anything similar? Is there something new on the windows domain that needs configuring? Do we need digital signing for the QNTC file system?

OS Version V7R3M0.
For testing, I'm using my profile which I set to *SECOFR with *ALLOBJ authority.


Thanks
Ron



Ron Hudson | Programmer / Analyst
+1.704.752.6513 x1324
www.invue.com

[Description: InVueLogo.gif@01CAA964.89E57320]


--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com