Symantec Privileged Access Management

 View Only
  • 1.  CA PAM TCP/UDP service for Secure CRT

    Posted Dec 04, 2019 11:59 PM

    Hi, 

    We have configured TCP/UDP service for secure CRT and when we try accessing, we are getting below error.

    Client application path provided : "C:\Program Files\VanDyke Software\Clients\SecureCRT.exe" /ACCEPTHOSTKEYS /L <User> /PASSWORD <Password> /P <First Port> /T <Local IP>"
    Please suggest if we have to do any modifications.
    Thank you.
    Regards,
    Namitha.S


  • 2.  RE: CA PAM TCP/UDP service for Secure CRT

    Broadcom Employee
    Posted Dec 05, 2019 12:22 AM

    Hello Namitha,

    Please share the full screenshot of the TCP/UPD service configured for connecting to secure CRT.

    Thanks,
    Reatesh.



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



  • 3.  RE: CA PAM TCP/UDP service for Secure CRT

    Posted Dec 05, 2019 01:22 AM
    Hi Reatesh,
    Here is the Config :

    Thanks,
    Namitha.S



  • 4.  RE: CA PAM TCP/UDP service for Secure CRT

    Broadcom Employee
    Posted Dec 05, 2019 12:26 AM
    Hi Namitha, Is it possible that you didn't configure a target account for autologin in the access policy? Another possible problem may be special characters in the password. Check the SecureCRT command line options on how special characters are handled, and try with a simple alphanumeric password.


  • 5.  RE: CA PAM TCP/UDP service for Secure CRT
    Best Answer

    Posted Dec 05, 2019 01:23 AM

    Hi Namitha,

    please try below path.

    "C:\Program Files\VanDyke Software\Clients\SecureCRT.exe" /ACCEPTHOSTKEYS /L /PASSWORD <Local IP>:<First Port> 

    or

    "C:\Program Files\VanDyke Software\Clients\SecureCRT.exe" /T /SSH2 /AUTH password /L CA Privileged Access Manager <Local IP>:<First Port> /PASSWORD %PASS%

    regards
    Ramesh




  • 6.  RE: CA PAM TCP/UDP service for Secure CRT

    Broadcom Employee
    Posted Dec 05, 2019 04:32 AM
    Hi Namita,

    Also look at the suggestion provided by Ralf, use a simple password without special characters and check if the login works.

    Thanks,
    Reatesh.

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