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/tre...pt/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
On Tue, 23 Dec 2003 16:12:45 -0500, "Sigitas"
<(E-Mail Removed)> wrote:
>
>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
>