The target process should use Socket.#ctor(SocketInformation) to create the duplicate socket instance.

If you call the Socket.#ctor(SocketInformation) constructor multiple times with the same byte array as the argument for each call, you will create multiple managed System.Net.Sockets.Socket instances with the same underlying socket. This practice is strongly discouraged.

If the process creating the socket uses asynchronous methods (erload:System.Net.Sockets.Socket.BeginReceive or erload:System.Net.Sockets.Socket.BeginSend), the process must first set the Socket.UseOnlyOverlappedIO property to true; otherwise, the socket is bound to the completion port of the creating process, which may cause an ArgumentNullException to be thrown on the target process.