Question : web  server sessions

we have a webserver appliucation that sends transactions to offsite webfarm fpr processing
we open a session do a batch close the session, and do it all over again and again
 we are allways hitting the same server on the remote site and not utlizing the other 6 servers in the farm and this is causing a bottleneck.

They  think that each session is created from our side (in tcp), and then we keep the session open until we have completed all the batch transactions. they are ubnder the impression that, we have the same session always open to send all the traffic, so its always to same 1 server in their end and  the load balancing is not working.

i know we open a session for each individual batch that we send
any clues or test that i can perform to get this resolved, and they assure me that its not a problem with the farm

Answer : web  server sessions

Ok, so, I'm not real sure what you mean by "sessions on our side are handled by SQL"...

 But, you have an app, I assume that connects via https, so its acting as a web agent (i.e. browser).  When it connects to the virtual server on the load balancer a session is created for that connection, futher when the connection is proxied from the LB to the webserver and subsequently the applications, another session is created that the web/app servers manage.  

So, to them it just appears as a single agent making multiple requests, and your probably making requests frequent enough from this same "agent" that the session doesn't idle long enough to timeout.

I don't know what kind of LB the other party has, but they will have to make and adjustment of some type to turn the idle timeout on your agent way down, or turn of affinity so each connection you make is treated as a separate connection.