What analysis we expect from partners/customers for troubleshooting SSH product issues?

What analysis we expect from partners/customers for troubleshooting SSH product issues?

When there's an issue with SSH products (Tectia Client/Server, PrivX), we need the below information for further investigation:
SSH Product
SSH Product Version
Source Operating System Name and Version
Destination Operating System Name and Version
Overview of Problem:
What is the source, and what is the destination?
Can the source connect to other servers?
Can the destination accept connections from other clients?
What is the use case?
What is not working?
Has it ever worked?
Is this a new or existing setup?
Has anything changed in the environment?
Debugging Output from the products
Can the problem be recreated?
Getting the above information before logging the case will help expedite the checking process much faster.


    • Related Articles

    • Recommendation from SSH on Tectia product upgrade

      As mentioned in admin manual, when upgrading a maintenance release of Tectia Server on Windows, usually no rebooting of the computer is needed. If they customer is using any version older than 6.4.12 currently, reboot is required. Before starting the ...
    • SSH solutions knowledge base

      For usage of SSH solutions like SSH Tectia Client/Server, PrivX, Universal Key Manager, please visit SSH knowledge base.