Socket.BeginAccept Method (Socket, Int32, AsyncCallback, Object)


The .NET API Reference documentation has a new home. Visit the .NET API Browser on to see the new experience.

Begins an asynchronous operation to accept an incoming connection attempt from a specified socket and receives the first block of data sent by the client application.

Namespace:   System.Net.Sockets
Assembly:  System (in System.dll)

[<HostProtectionAttribute(SecurityAction.LinkDemand, ExternalThreading = true)>]
member BeginAccept : 
        acceptSocket:Socket *
        receiveSize:int *
        callback:AsyncCallback *
        state:Object -> IAsyncResult


Type: System.Net.Sockets.Socket

The accepted Socket object. This value may be null.

Type: System.Int32

The maximum number of bytes to receive.

Type: System.AsyncCallback

The AsyncCallback delegate.

Type: System.Object

An object that contains state information for this request.

Return Value

Type: System.IAsyncResult

An IAsyncResult object that references the asynchronous Socket object creation.

Exception Condition

The Socket object has been closed.


Windows NT is required for this method.


The accepting socket is not listening for connections. You must call Bind and Listen before calling BeginAccept.


The accepted socket is bound.


receiveSize is less than 0.


An error occurred when attempting to access the socket. See the Remarks section for more information.

Connection-oriented protocols can use the BeginAccept method to asynchronously process incoming connection attempts. Accepting connections asynchronously gives you the ability to send and receive data within a separate execution thread. This overload allows you to specify the accepted socket in the acceptSocket parameter. If this parameter is null, the accepted socket is created by the BeginAccept method. You can specify the number of bytes to accept in the initial transfer in the receiveSize parameter.

Before calling the BeginAccept method, you must call the Listen method to listen for and queue incoming connection requests.

You must create a callback method that implements the AsyncCallback delegate and pass its name to the BeginAccept method. To do this, at the very minimum, you must pass the listening Socket object to BeginAccept through the state parameter. If your callback needs more information, you can create a small class to hold the Socket and the other required information. Pass an instance of this class to the BeginAccept method through the state parameter.

Your callback method should invoke the EndAccept method. When your application calls BeginAccept, the system usually uses a separate thread to execute the specified callback method and blocks on EndAccept until a pending connection is retrieved.

EndAccept returns a new Socket object that you can use to send and receive data with the remote host. You cannot use this returned Socket to accept any additional connections from the connection queue. If you want the original thread to block after you call the BeginAccept method, use WaitHandle.WaitOne. Call the Set method on a ManualResetEvent in the callback method when you want the original thread to continue executing.

The system may also use the calling thread to invoke the callback method. In this case, the CompletedSynchronously property on the returned IAsyncResult will be set to indicate that the BeginAcceptmethod completed synchronously.

For additional information on writing callback methods, see Marshaling a Delegate as a Callback Method.

To cancel a pending call to the BeginAccept method, close the Socket. When the Closemethod is called while an asynchronous operation is in progress, the callback provided to the BeginAccept method is called. A subsequent call to the EndAcceptmethod will throw an ObjectDisposedException to indicate that the operation has been cancelled.


You can use the RemoteEndPoint property of the returned Socket object to identify the remote host's network address and port number.


If you receive a SocketException, use the SocketException.ErrorCode property to obtain the specific error code. After you have obtained this code, refer to the Windows Sockets version 2 API error code documentation in the MSDN library for a detailed description of the error.


This member outputs trace information when you enable network tracing in your application. For more information, see Network Tracing in the .NET Framework.


The execution context (the security context, the impersonated user, and the calling context) is cached for the asynchronous Socket methods. After the first use of a particular context (a specific asynchronous Socket method, a specific Socket instance, and a specific callback), subsequent uses of that context will see a performance improvement.

The following code example opens a socket and accepts an asynchronous connection. In this example, the socket accepts the initial 10 bytes of data and the acceptSocket parameter is null, which forces the BeginAccept method to create the accepted socket. The number of bytes received and the data are displayed on the console by the callback delegate. See BeginReceive for a description of how the remaining data is received.

No code example is currently available or this language may not be supported.

.NET Framework
Available since 2.0
Return to top