Question : RIS 2003 error:  PXE-E53: No boot filename received

I have just set this up, it's never worked right.  It looks like it gets stuck looking for a DHCP server.  The DHCP server is working fine.  I recieved no errors doing the risetup or riprep.  grovel and RIS services are working.  I'm pretty stuck.  I even did a DHCP reservation for this pc's MAC address.  Any ideas will be helpful.

Thanks in advance.

Answer : RIS 2003 error:  PXE-E53: No boot filename received

The Boot Agent received a DHCP or BOOTP offer,  but has not received a
valid filename to download. If you are using PXE, please check your PXE
and BINL configuration. If using BOOTP, be sure that the TFTP service
is running and that the specific path and filename are correct.

this is from the http://www.microsoft.com/windows2000/docs/remosadmin.doc


Trouble Shooting RIS client issues (PXE)
Problem/Error: PXE client does not connect to the RIS server (never receives a prompt to press F12). In addition, the client may receive a "PXE-E53:  No Boot filename received from BINL, DHCP, or BOOTP" error mesage.
Proposed Actions/Solutions:
?      Check the PXE revision of the client, especially in the case where a router separates the client and the RIS server. The currently recommended version is 99N or greater.
?      Check to see that the RIS services are running (BINL, TFTP, and the Groveler service). To do this, click Start, click Run, type risetup -check, and then click OK.
?      Check the RIS server to see if the "Answer all Clients" or "Answer only known clients" option is enabled. If the client is not pre-staged in Active Directory and the RIS server has the "Answer only known clients" option enabled, the RIS server does not respond. For more information, please refer to the "Pre-Staging Client Computers" section of this white paper.
?      Verify that the RIS server is authorized in the domain. RIS servers do not respond if the server is not authorized. Use the DHCP Management snap-in to view authorized servers. If the RIS server is not displayed in the list of authorized servers, use the following steps to authorize the server and stop and start the RIS service:
a.      Click Start, click Run, type cmd, and then click OK.
b.      At the command prompt, type the following commands pressing ENTER after each command:
net stop binlsvc
net start binlsvc
c.      To verify the server is authorized, check the application event log for an event ID 1045.
?      If a router separates the client and RIS server, and clients on the same segment as the RIS server are answered but clients on other segments are not, check the following:

Check to see if the router is forwarding DHCP or IP requests. A good test for this is to see if other clients (Windows 95/98, Windows NT, and so on) can obtain an IP address from that server. If the clients can obtain an IP address, the router may be misconfigured. Check to see if the router has an IP helper address for the RIS server (for more information, refer to the "Deploying RIS Servers" section of this document).
?      If RIS and DHCP are on the same computer, make sure the ResponseDelay value is set to 0. This value is located in the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc\Parameters