Unable to write data to the transport connection & Timeout

[Steve - DND]

We are continually receiving timeout, and "Unable to
write data to the transport connection" errors while using the
System.Net.Http WebRequest class from an ASP.Net web page. Below are the two
errors we continue to
receive:

Source: System
Message: The operation has timed-out.
Target Function: System.Net.WebR esponse GetResponse()

Stack Trace:
at System.Net.Http WebRequest.GetR esponse()
at Transaction.Pro cess()

and

Source: System
Message: Unable to write data to the transport connection.
Inner Exception: System.IO.IOExc eption: Unable to write data to the
transport connection. ---> System.Net.Sock ets.SocketExcep tion: An
established connection was aborted by the software in your host machine
at System.Net.Sock ets.Socket.Begi nSend(Byte[] buffer, Int32 offset, Int32
size, SocketFlags socketFlags, AsyncCallback callback, Object state)
at System.Net.Sock ets.NetworkStre am.BeginWrite(B yte[] buffer, Int32 offset,
Int32 size, AsyncCallback callback, Object state)
--- End of inner exception stack trace ---
at System.Net.Sock ets.NetworkStre am.BeginWrite(B yte[] buffer, Int32 offset,
Int32 size, AsyncCallback callback, Object state)
at System.Net.TlsS tream.BeginWrit e(Byte[] buffer, Int32 offset, Int32 size,
AsyncCallback asyncCallback, Object asyncState)
Target Function: System.IAsyncRe sult BeginWrite(Byte[], Int32, Int32,
System.AsyncCal lback, System.Object)

Stack Trace:
at System.Net.TlsS tream.BeginWrit e(Byte[] buffer, Int32 offset, Int32 size,
AsyncCallback asyncCallback, Object asyncState)
at System.Net.Conn ection.BeginWri te(Byte[] buffer, Int32 offset, Int32 size,
AsyncCallback callback, Object state)
at System.Net.Conn ectStream.Begin Write(Byte[] buffer, Int32 offset, Int32
size, AsyncCallback callback, Object state)
at System.Net.Conn ectStream.Write (Byte[] buffer, Int32 offset, Int32 size)
at Transaction.Pro cess()

Do I need to contract out someone to develope a solid socket object that I
can interface with, whether it be .Net or COM? It's critical that these
connections make it through in real-time, and the fact is, that the above
two
errors happen to about 5% of our requests. I have verified that when
requests timeout, it has nothing to do with the receiving party. They never
even receive the request from us. The second error occurs seemingly at
random, and while it usually makes it to the target server, it drops off
before we can receive the response.

Any tips, or advice would be appreciated, and there is nothing between the
server and the internet(no proxies, no web services) other than the firewall
which works perfectly fine.

Thanks,
Steve