PXE-53 Error: No boot filename received - Cause(s)?

We have setup several Windows 2003 RIS servers in the past, but this
one is stumping us.

Windows 2003 setup properly as a DC (second of two on the network),
DHCP (only one, no DHCP server conflict), and RIS

Client has a PXE NIC

The client searches for a good long time at the "DHCP" prompt, then
quits and reports the error "PXE-53: No boot filename found." I've
seen other articles about this, but no actual causes in the responses.
Is there a typical cause for this error?

Thanks,

DP

This is the error code description from the Intel spec:

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.

-nm

Yes, all of that has been checked. The file name is valid and the BINL config is OK.

"nmayes" <nwmayes@gmail.com> wrote in message news:<1113514372.612117.127110@g14g2000cwa.googlegroups.com>...
> This is the error code description from the Intel spec:
>
> 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.
>
> -nm

I'm having the same issue with ADS/VSMT. My setup was working fine with PXE
running on the ADS server and DHCP on one of the DC's. All of the sudden I
am getting the PXE-53 error and nothing functions.

Thanks

"DP" wrote:

> We have setup several Windows 2003 RIS servers in the past, but this
> one is stumping us.
>
> Windows 2003 setup properly as a DC (second of two on the network),
> DHCP (only one, no DHCP server conflict), and RIS
>
> Client has a PXE NIC
>
> The client searches for a good long time at the "DHCP" prompt, then
> quits and reports the error "PXE-53: No boot filename found." I've
> seen other articles about this, but no actual causes in the responses.
> Is there a typical cause for this error?
>
> Thanks,
>
> DP
>

Unless you intend to boot the computer from a network device, you should turn off the network boot option in the list of bootable devices in the BIOS. Not good enough to move it down in the priority list, you have to delete it.