Hey there! Let's figure out why only the requesting client is getting your broadcast data—chances are it's not TCP packetization causing the problem, but how you're managing your Socket collection. Here's what to check and fix:

1. First: Verify Your Socket Collection is Correct #

Before diving into code fixes, confirm that socketArray actually contains all connected clients, not just the one making the request. Add a quick debug line right before your foreach loop:

Console.WriteLine($"Total connected sockets: {socketArray.Count}");
foreach(Socket sct in socketArray)
{
    Console.WriteLine($"Socket endpoint: {sct.RemoteEndPoint}");
}

If this only shows the requesting client's endpoint, your issue is that disconnected clients aren't being removed from the array, or new connections aren't being added properly.

2. Handle Socket State & Send Exceptions #

When you call Send() on a Socket that's already disconnected (or in an invalid state), it will throw an exception—and if you don't catch it, the foreach loop will terminate immediately, leaving other clients untouched. Wrap your send logic in a try-catch block, and check socket validity first:

// Convert to a list to avoid issues if the collection changes mid-loop
foreach(Socket sct in socketArray.ToList())
{
    // Skip sockets that aren't connected
    if (!sct.Connected)
    {
        socketArray.Remove(sct);
        sct.Close();
        continue;
    }

    try
    {
        sct.Send(data);
    }
    catch (SocketException ex)
    {
        // Log the error and clean up the dead socket
        Console.WriteLine($"Failed to send to {sct.RemoteEndPoint}: {ex.Message}");
        socketArray.Remove(sct);
        sct.Close();
    }
}

3. Fix Thread Safety for Your Socket Collection #

Multi-client servers handle connections/disconnections on separate threads (e.g., your Accept() thread). If socketArray is a regular List/Array, modifying it (adding/removing sockets) while iterating can cause partial loops, skipped elements, or exceptions. Use a thread-safe collection like ConcurrentBag<Socket> or wrap all access to socketArray with a lock:

// Using a lock to protect collection access
lock(socketArray)
{
    foreach(Socket sct in socketArray.ToList())
    {
        // Your send logic here
    }
}

// When adding a new socket:
lock(socketArray)
{
    socketArray.Add(newClientSocket);
}

4. Why TCP Packetization Isn't the Culprit #

TCP is a stream-based protocol, so packetization (how data is split into segments) happens at the OS level—it won't prevent data from reaching other clients. Your issue is about which clients you're sending to, not corrupted or missing data in transit. So you can rule out TCP packetization as the root cause here.

Give these steps a try, and let me know if you run into more issues!

内容的提问来源于stack exchange，提问作者Emirhan Özsoy