In this unique seminar you’ll learn how to write a TDI client driver: A kernel mode driver that uses the network stack to communicate with other systems.

Level

Intermediate

Audience

Developers of Windows kernel mode drivers who need to interface directly with an existing TDI transport layer (TCP/IP, NetWare, AppleTalk, etc.). 

Description

Network protocol drivers implement an upper-edge interface known as the Transport Driver Interface (TDI). Applications using WinSock can only communicate with protocol drivers implementing TDI. A kernel-mode device driver can also make use of this interface to communicate with a protocol driver. A driver that communicates with a network protocol driver implementing the TDI interface, is known as a TDI client driver.

Topics

• TDI driver architecture

• Address objects

• Connection endpoints

• Event handlers

• Opening a connection to a remote endpoint

• Sending data

• Receiving data

• Closing a connection

Prerequisites

DRV221: Windows Network Drivers, or direct experience writing NDIS miniport or intermediate drivers. Experience with the WinSock API is also helpful.

Windows versions

Windows Server 2003, Windows XP, Windows 2000

Duration and formats

2 days with labs
1 days lecture only

Labs

Hands-on labs are highly recommended for this seminar. Students will write and debug a fully functional TDI client driver and demonstrate communication with a remote system.