Hi,

It's ages sinces I worked with this but I'm sure Bob is right in that you should spawn another socket to handle the request and keep the listening port free. I'm also sure that you can do this without worrying about the multithreading aspect. There's some sample code for creating a socket pool for this scenario somewhere on MSDN but I can't find it right now.
HTH,
Viv

>I was afraid you were going to say something like this. Creating a multi-threaded DLL just kind of give me the shivers, since I barely know much about TCP and port communications as it is. Any good resources you can recommend before I go Googling?
>
>> Most TCP type schemes like this would use two ports, one to make the original connection, then a seperate thread to handle that request so the original port could continue to listen for more connections. In this senerio you may want to use a multi threaded Dll.
>>
>>Bob