Operation
TDI_CONNECT is a request message a client issues to indicate a connect request.
Note TdiBuildConnect is the macro a client uses to fill in the IRP.
For a local node client to establish a connection, it must associate an idle local connection endpoint with an address object before making a connect request. If the specified endpoint is active or nonexistent, the request fails with an error code. For the connect request to succeed, the remote node client must have an open listen request or a registered ClientEventConnect function that can receive connect events from the driver.
Along with the request message, the TDI client must provide input and output buffers for the IRP, as well as a status block structure the driver uses to write information about the request. These items are described below. For more information about the members of the IRP related to a connect request, see TdiBuildConnect.
Input
TDI_CONNECTION_INFORMATION structure
Output
TDI_CONNECTION_INFORMATION structure
I/O Status Block
The driver fills in the Status member of the IRP with one of the following TDI status codes:
STATUS_BAD_NETWORK_PATH
STATUS_INSUFFICIENT_RESOURCES
STATUS_INVALID_CONNECTION
STATUS_PENDING
STATUS_REMOTE_NOT_LISTENING
STATUS_REQUEST_TIMED_OUT
STATUS_SUCCESS
For more information about status codes, see Part II, Chapter 10.
See Also