Symantec Privileged Access Management

 View Only
  • 1.  Secure CRT Issue

    Posted Jul 15, 2019 11:50 PM
      |   view attached

    SecureCRT version is 8.5.3

     PAM version is 3.2.4

    In our environment with the same Secure CRT client, in direct login, there is no issue on display. in our test environment also it is not getting the issue using the same client login same machine using the same secure Crt but The issue is only when we login with production PAM

    For instance, in the first login, we have to face the issue which I attached

    Please, can you suggest us that valid secure CRT Application path?





    ------------------------------
    Network and security Engineer technical associative
    Cas Trading House
    ------------------------------


  • 2.  RE: Secure CRT Issue

    Broadcom Employee
    Posted Jul 16, 2019 09:59 AM
    ​Hi Sudip, Another customer ran into such a problem with a TCP/UDP service using the SSH protocol. This is currently under review by PAM Engineering. Please open a support case if not done yet.


  • 3.  RE: Secure CRT Issue

    Posted Jul 16, 2019 11:55 AM
    Thank you,
    Now, We solve the issue. :)

    ------------------------------
    Network and security Engineer technical associative
    Cas Trading House
    ------------------------------



  • 4.  RE: Secure CRT Issue

    Posted Jul 17, 2019 08:02 AM

    Hi Sudip,
    Could you please post your resolution? I think it may help us also.
    Christo​




  • 5.  RE: Secure CRT Issue
    Best Answer

    Broadcom Employee
    Posted Jul 17, 2019 09:21 AM
    Hello Sudip,

    We were able to resolve this problem in the client end yesterday.

    We had to disable to secondary Network Card on both the CA PAM nodes and after this we did not come across this problem.

    The way the secondary network card needs to be configured has to be done properly, else the results were bad as we did see, the other problem of the bad network configuration was the the VIP was only redirecting the request to the secondary PAM node always, even this problem was fixed after disabling the wrongly configured secondary network card.

    Thanks,
    Reatesh.

    ------------------------------
    Principal Support Engineer
    Broadcom
    ------------------------------