Introduction

Yes. EndReceive returning 0 means the remote peer has performed a graceful shutdown of its sending side, so there is no more data to read. That can happen even when the local socket object still looks present and the connection has not yet been fully torn down from every perspective.

What zero bytes means in TCP

In stream sockets, a read of zero bytes is the end-of-stream signal. It does not mean "try again later." It means the peer has closed its send direction, and your side has reached EOF for receives.

That is the same core meaning whether you use synchronous Receive or the older asynchronous BeginReceive and EndReceive pattern.

1void ReceiveCallback(IAsyncResult ar)
2{
3    Socket socket = (Socket)ar.AsyncState!;
4    int bytesRead = socket.EndReceive(ar);
5
6    if (bytesRead == 0)
7    {
8        Console.WriteLine("Remote side closed the connection gracefully.");
9        socket.Close();
10        return;
11    }
12
13    Console.WriteLine($"Read {bytesRead} bytes");
14}

In other words, zero is a real signal, not an anomaly.

Why it can feel like the socket is still connected

TCP allows half-closed connections. One side can stop sending while still being able to receive, at least until the session is fully closed. The local socket object may still exist, and some state checks may not yet make the situation look obviously dead.

That is why the question often sounds confusing. The application thinks, "My socket object is still here," while the protocol state says, "There is no more incoming data from the peer."

For receive logic, the protocol meaning wins. A zero-byte read should be treated as connection closure for the receive path.

Do not wait for more data after zero

Once EndReceive returns zero, your code should stop expecting normal payload bytes from that socket. Continuing to read in a loop usually just delays cleanup and complicates control flow.

The right response is typically:

• finish any final shutdown logic
• release socket resources
• notify the rest of the application that the peer closed the connection

Distinguish zero from temporary lack of data

A temporary lack of data on a blocking receive does not appear as zero. It appears as the call waiting until data arrives, the connection closes, or an error occurs. On non-blocking sockets, the "no data yet" case appears as a would-block style error or exception pattern, not as a successful zero-byte receive.

That distinction is important. Zero is not "nothing available right now." Zero is EOF.

Zero bytes is different from an error

A reset, timeout, or network failure usually appears as an exception, not as a successful receive of zero bytes. That distinction is useful in diagnostics. Zero means the peer closed cleanly. An exception means the connection failed in a less orderly way or the operation could not complete normally.

Common Pitfalls

• Treating EndReceive == 0 as if it were a harmless empty packet.
• Continuing to issue receive calls after the peer has already closed its send side.
• Confusing an existing local socket object with an active bidirectional stream.
• Using ad hoc connection-state checks instead of trusting the actual receive result.
• Forgetting that TCP supports half-closed connections.

Summary

• 'EndReceive returning zero is the normal TCP end-of-stream signal.'
• It means the remote peer closed its sending side gracefully.
• That can happen even if the local socket object still exists.
• Zero is not the same as "no data yet" on a still-open stream.
• Treat it as closure for the receive path and clean up accordingly.