Highlighted
Absent Member.
Absent Member.
2954 views

Error: Communication error: The Client failed to send packet. The socket has been shut down.

Jump to solution

Steps followed to installed Load Agent on AWS.

1. Firewall Exception from controller for port 50500 , 54345, 443 and 3389 on load agent machine.

2. Installed Load Runner Setup [ as Load agent Process is also a part of Load Runner Setup]

3. Allowed all the programs [Agent Process, Agent Service.. etc] from Windows Firewall.

4. Tried to connect from Load Controller. Error received on controller is 

Communication error: The Client failed to send packet. The socket has been shut down.

As per OPs team, the agent is trying to establish a connection back to a server 54.xxx.xx.xxx[Unknown AWS IP] on port 10051 and failing eventually where as this particular server is unknown to us.

 

Please tell how do i have to install or configure MI LISTENER or AGENT PROCESS over firewall.

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.
Absent Member.

Re: Error: Communication error: The Client failed to send packet. The socket has been shut down.

Jump to solution

The solution to this problem was there was some discrepancies from the Firewall and IT team.

We were able to telnet into the agents but as on the application layer our Loadrunner tool was not able to communicate with Agents.

Re-applying the firewall exception made it PASS.

View solution in original post

0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

Re: Error: Communication error: The Client failed to send packet. The socket has been shut down.

Jump to solution

The solution to this problem was there was some discrepancies from the Firewall and IT team.

We were able to telnet into the agents but as on the application layer our Loadrunner tool was not able to communicate with Agents.

Re-applying the firewall exception made it PASS.

View solution in original post

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Error: Communication error: The Client failed to send packet. The socket has been shut down.

Jump to solution

Hi,

What ports did you open bi-directional? 

 

I have a AWS load gen and a controller behind firewall and would like to understand which ports needs to be open bi-directional and why?

 

Thanks

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.