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

[James Pulley]

This post is being removed as a cross forum post.  Please do not respond to this thread as all answers will be removed.

Please see forum guidelines regarding cross forum posts to avoid this issue in the future

On Thursday, December 17, 2015 at 12:32:21 PM UTC-5, Nirmit Srivastava wrote:

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

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.

[Narasimha Naidu]

Hi,

 

 i think ur changes in firewall configuration please dont do that one.