Since it's a blank screen and not prompting for a password, then I suspect the cause is a network communication issue from the workstation/client to the manager/ssh-relay server. In order to find out more details, you could open the downloaded .jnlp file in a text editor and there will be two "property" xml elements, with one "name" attribute being the "...pamHost," which represents the sshrelay connection info supplied to the client.

So with that property value of the "pamHost," you'll know the ip/dns/port connection information that the client is trying, so I would suggest using that to rule out any potential communication issues from the client side first. For example, perhaps it is a DNS Address that can't be resolved properly to an ip address, or perhaps there is a firewall blocking communication from client to sshrelay server via port 2222, etc.

Otherwise, I recommend opening up a Service Request with Support to investigate with you.

Since it's a blank screen and not prompting for a password, then I suspect the cause is a network communication issue from the workstation/client to the manager/ssh-relay server. In order to find out more details, you could open the downloaded .jnlp file in a text editor and there will be two "property" xml elements, with one "name" attribute being the "...pamHost," which represents the sshrelay connection info supplied to the client.

So with that property value of the "pamHost," you'll know the ip/dns/port connection information that the client is trying, so I would suggest using that to rule out any potential communication issues from the client side first. For example, perhaps it is a DNS Address that can't be resolved properly to an ip address, or perhaps there is a firewall blocking communication from client to sshrelay server via port 2222, etc.

Otherwise, I recommend opening up a Service Request with Support to investigate with you.

Since it's a blank screen and not prompting for a password, then I suspect the cause is a network communication issue from the workstation/client to the manager/ssh-relay server. In order to find out more details, you could open the downloaded .jnlp file in a text editor and there will be two "property" xml elements, with one "name" attribute being the "...pamHost," which represents the sshrelay connection info supplied to the client.

So with that property value of the "pamHost," you'll know the ip/dns/port connection information that the client is trying, so I would suggest using that to rule out any potential communication issues from the client side first. For example, perhaps it is a DNS Address that can't be resolved properly to an ip address, or perhaps there is a firewall blocking communication from client to sshrelay server via port 2222, etc.

Otherwise, I recommend opening up a Service Request with Support to investigate with you.

Hi Mishra,

Have you got the solution, If yes can you guide me on it.