Brad, I do this all the time!
First, your client with no OS needs a NIC with a Boot ROM. If your NIC does not have a Boot ROM you can use the Remote Boot Floppy Generator (rbfg.exe) that comes with Win2K. Next, I install 3Com's DynamicAccess Boot Services software (TFTP, BOOTP, PXE, Bootptab file, Boot Image Editor) on the server (Win9x, NT4 or Win2K.)
In a nutshell here's how the process works.
Depending on your network configuration, you select a protocol. BOOTP for static IP, PXE/DHCP for dynamic IP. I'll use PXE as the example. At the server, use the Boot Image Editor to create an image that will contain all the necessary drivers and drive mappings to the Win2K pro Cab files.
Configure your client's Boot ROM to Boot PXE. The client connects to the network, looks for the PXE server, PXE server gets client's IP address from DHCP Server and it looks for an entry in the Bootptab database and to find the image that has been assigned to the client. TFTP then downloads the image to the client and Win2K pro gets installed locally on the client machine.
I have a step by step tech paper describing the entire process using Win98. I can email it to you if you'd like.
For more info on Boot Services software see www.3com.com/managedpc
Lee