Seeking your opinion on this actual scenario (still unresolved as of this writing): an external branch windows server connected to an AS400(model 820) via IPVPN connection with 512 kbps bandwidth have a "CONNECTION FAILURE" message but other Windows Application used by the branch that's still connected to AS400 as backend server runs smoothly. The Windows application that is at issue here is a Report Download facility that's connected to the AS400 which previously was working but there was an incident wherein the Network connectivity of the branch was down and when it became normal, the branch could not anymore use the windows application to download reports, there's the message "CONNECT FAILED ERROR NO. 53" message. Other Windows Applications used by the branch that's connected to the AS400 as backend server are working after the "network down incident" except for this windows application to download reports. Is it possible that this connection failure message when doing report downloading is due to the sudden network problem of the branch that when the network connection returned back to normal, when the branch repeated to do the report download activity, the previous "abruptly ended" report download activity still persists and is causing the problem. The reports being downloaded by the branch from AS400 are linked to QDLS where the concerned branch has an enrolled folder in QDLS and the Windows Application used by the branch is accessing this folder to come up with the reports. Is there a command in AS400 to check on this scenario? I already check the ip address of the branch server and this is defined in the AS400. Also adviced the branch do a "PING" if the branch can detect the AS400 and the ping was successful and vice-versa, i can also ping the branch. Do you have suggestions on how to address this issue using other AS400 CL commands? Thanks.
Software/Hardware used: i-Series model 820, OS V5R3M0