Connection refused when trying to connect RDP

[Sona T]

Dear Team,

The user started facing the issue below in PAM while RDP to the device. Previously, it was working fine.

Also, the same user is working fine on another laptop.

They tried re-installing PAM, but it didn't work.
We have already installed java 8 on the client machine.

Please suggest how to resolve this issue.

CA PAM version: 4.0.1

We tried the below article but the issue still persists ,kindly help me with a resolution
Debugging Connection refused when trying to connect to 127.0.0.200 ... errors

Broadcom		remove preview
Debugging Connection refused when trying to connect to 127.0.0.200 ... errors Resolution Attached is a java utility that launches a server socket on a specified local IP and port. This requires Java to be installed, which is required anyway for the PAM access methods to work. If you use a browser to logon to PAM, you must have a JRE installed and enabled the Java plugin in the browser. View this on Broadcom >

[Ralf Prigl]

Hello, I assume that when you say "re-installing PAM", you mean to say that you reinstalled the PAM Client. The client uses its own private JRE, it doesn't matter what other JREs you have installed on the client machine. When you say you tried the article, did you use the tool and found that you have no problem connecting to local IP 127.0.0.200, only the PAM RDP client has this problem?

[Sona T]

Hello Ralf,

Thankyou for responding , yes we have issue with PAM RDP client , kindly find the enclosed logs , please let me know if it would be resolved

[Ralf Prigl]

Hello Sona, This is not a Support channel and we do not want you to attach log files for review to community threads. It would be ok to take an error message or exception stack trace out of a log file and post it here, to see if someone else recognizes this right away as a known problem that has a known workaround or solution. But in general, when it gets to the point where log review is needed, you should open a case with PAM Support. Once the case is resolved, it would be valuable to share the solution in the community thread you had started on the topic.
The exception in the log does suggest that there is a problem with the local connection to IP 127.0.0.200. Why did you attach the server socket zip file? Anyone can get that from the KB article. What would be of interest is for you to use this tool and see whether you can make successful connections to the local IP. If it doesn't work with the tool, it won't work with the PAM client and you would need to open up the local firewall to let the connections succeed.