I couldn't figure out where to place this question, so I decided to put it in General. Little by little I am compiling all the peices of this massive application that I am creating. Although I still have one very vital peice that is a little vague to me, and that is Remoting. I found some samples on the subject of Remoting, and watched some very vague and confusing videos. I think I have a general idea, but I still feel like I am on shaky ground. In VB6 the concept was pretty simple, Use one TCP WinSocket as a Listener Socket and pass the ConnectionID to a secondary socket for connection, thereby leaving the listening port open for the next connection request. It almost appears to have a similar flow in .Net, but...I am a little confused. At first glance the TCPListener.AcceptSocket appears to create a new Socket Object...but then, I can't see that a new port was assigned to it, so I can't tell if the Listener Port is busy after the AcceptSocket command and will refuse to accept another connection. I have some code written, but it's getting complicated and I didn't want to waste several hours peicing it all together to realize I was all wrong about it.

In short (I know, too late), does anyone have a site or sample code I can view that breaks down TCP communication (Or Remoting as .Net like to call it) into an easy to understand way?