Thanks Thelonius - but isn't there a fundamental flaw in that approach? You are sending on based on some kernel chosen port, and then listening for replies on a specified port.

How does the peer know which port the sender is listening on?

That's why I was trying to use one socket object. I hope that will work, or I don't know how to listen for what I sent?