Unfortunately right now I’m not able to reproduce this error. I’ve only tried it in a console app on a loopback adapter so far but as I was expecting it is not a general problem with networkComms.net. As such we need to know a little bit more about your set-up and what you’re trying to do.
What platform is this running on at the client and server ends? What sort of physical network links the client and server? Is the object your trying to send a custom object and is it quite large? Is there anything you can think of that is particularly unusual about your set-up? Is the error thrown on all sends or just some of the time?
This should hopefully be a relatively simple problem to solve once we know where the issue is.