Has anyone else seen WinSock Error 10055 WSAENOBUFS when working with .NET Remoting? 

.NET is a great abstraction layer, arguably the best, but I tell ya, I spend more time with Packet Sniffers and running around at the levels of:

A. Threading
2. Sockets

than I ever used to...it feels like these two core OS areas are being stressed more now that .NET enables us to built software bigger, better, faster.  Our abstraction layer is creaking under the heavy load of either my creativity or my ignorance.