WCF / ASMX :: Intermittant Error: "A Connection Attempt Failed Because The Connected Party Did Not Properly?

I'm having a doozy of a problem, and can't find a solution. I have a WFC Web Service installed to a pair of servers, and accessed through a load balancer. I am accessing the service from an ASP.NET client app, also via WCF. The Client is not load balanced.I'm getting an intermittant error:

(Inner Most Exception) System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:80(Middle Exception) System.Net.WebException: Unable to connect to the remote server(Outer Exception) System.ServiceModel.EndpointNotFoundException: Could not connect to http://<MYSite>/<MYApp>/<MYService>.svc.TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:80.

I can reproduce this error with about 20% reliability if I execute the exact same page request on the client from 2 browsers at the same time. When the problem occurs, the successful page request returns in about 5 seconds, and the failed page request returns in about 30 seconds.I'm guessing that there is some additional latency when the load balancer decides to switch my session to another server, and that is making some timeout setting on my client to be exceeded. I need to research this performance characteristic... any thoughtsbut its not my core question.My core question is... Exactly what setting can I tweak to increase the "period of time" the "connected party" is allows to "properly respond".This is the basicHttpBinding configuration I am using on both sides of the communication:

<basicHttpBinding>
<binding name="LongerTimeout"
sendTimeout="03:00:00"
maxReceivedMessageSize="2147483647"
maxBufferPoolSize="2147483647">
<readerQuotas maxArrayLength="2147483647" maxStringContentLength="2147483647"/>
</binding>
</basicHttpBinding>

I've seen some indication that setting the receiveTimeout value on the server may help, but I set this to 1 second in a test environment, and was unable to reproduce the problem, leads me to believe its not worth a production environment change to verify this.