Problem while access website through load balancer

Did you make the trace on the client or server side of the loadbalancer? Usually a loadbalancer will terminate the TCP session of the client to look into the HTTP request, so that it can make a loadbalancing decision based on the content of the HTTP request (think of cookie persistency as an example why this is needed).

Then I can think of two things that might be going wrong in your setup.

1. The loadbalancer is one-armed, but you do not NAT the source address of the client. This means traffic from the server goes back to the client instead of to the loadbalancer to change the real server IP address back to the virtual address.

2. Or the loadbalancer tries to open a connection to the server but for whatever reason does not succeed and therefor gives up after a while. In the mean time the client had retransmitted its request a couple of times.

In loadbalanced scenarios, it is always best to make traces on the client-side as well as the server-side of the loadbalancer to be able to follow its behavior.