RIS PXE-E53: No boot filename received ? - what is a file name ?

  • Thread starter Thread starter Sigitas
  • Start date Start date
S

Sigitas

Hello

I installed RIS server. W2k, AD, DNS is running fine. DHCP is on Linix.

When I start the client machine and try to communicate with RIS server I get
an error:

PXE-E53: No boot filename received
PXE-M0F: Exiting Broadcom PXE ROM.

After searching some newsgroups i found some info:
" PXE-E53: No boot filename receivedPXE-M0F: Exiting Broadcom PXE
ROM.Cause:The DHCP service did not provide the name of a boot file.Solution
Ensure that the filename command is correctly specified in the
/etc/dhcpd.conf file on the PXE server"Can anybody tell me what is a default
RIS boot filename? Ar any other ideas how i can solve this issue?thanxs
 
OK, I've never used a linux DHCP server so I don't have first-hand
experience with your setup.

Look closely at the client, does it get an IP address before the error?
Do your other network clients get IP addresses?
Are you trying to RIS across a router? Through VLANs?
Has RIS ever worked?

Is the RIS server authorized?
Is the little box "respond to client requests" checked?
Try Start>Run>RISETUP -CHECK>OK on the RIS server.

The file the client is looking for: \Oschooser\i386\Startrom.com

I have used this article in the past along with a packet sniffer to find RIS
problems:

Description of PXE Interaction Among PXE Client, DHCP, and RIS Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;244036
 
Here is some additional info to Scott's answer

You need to configure some dhcp options on the linux dhcp,
the options are 66 (server-name) and 67 (filename).

In dhcpd.conf add the options:
server-name "london.lcab.net";
filename "\OSChooser\i386\startrom.com";

Some linux dhcp servers has problems with backslashes in that case you
may change to
filename "/OSChooser/i386/startrom.com";

If that dont help, then copy the startrom.com from
\\server\reminst\OSChooser\i386\startrom.com to
\\server\reminst and change the 67 option to:
filename "startrom.com";

If the dchp is on a different subnet (or vlan) you need this option
(which dont seems to be a standard, at least according to RFC2132, but
works great)
next-server 192.168.9.200;


Here are some good articles about DHCP, RIS and PXE

Bootp and dhcp parameters
http://www.iana.org/assignments/bootp-dhcp-parameters

RFC 2132 - DHCP Options and BOOTP Vendor Extensions
http://www.faqs.org/rfcs/rfc2132.html

Technical Guide to Remote Installation Services
http://www.microsoft.com/technet/tr...nol/windows2000serv/deploy/depopt/remosad.asp

Using Dynamic Host Configuration Protocol Options 60, 66, 67 to Direct
PXE Clients to RIS Servers May Fail
http://support.microsoft.com/?kbid=259670


regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net
 
Thanks Guys... I really appreciate your comments! I'll try to work on this
issue this week.
 
If it helps, I've just been messing around with my RIS and got this error which turned out to the be the DHCP server service enabled on the RIS server. I disabled the server and all is fine again. I'm using my File and Printer server as the DHCP server.
 
CTRL + ALT + INSERT ; after you click connect ( cd/dvd or .iso ) in console you click CTRL + ALT + INSERT (you may try something with F1 eventually)
 
Back
Top