Assume you're trying the server component in poser, client should work ok.

Running the server component of the simple socket code will cause a lock up because it doesn't return control back to Poser. If the server code is edited to jump out of the loop after the first successful connection you should see control pass back to Poser once the client has completed its connection and the script terminates. This is no good for your application, it was just intended as a basic example. Somekind of non blocking listener function is required for the server component that runs in the background. Possibly the wx timer can do this? I can't access tromnek's sample code so may this is already explained there.