It's also possible to get the "No boot file name.." error if your PXE nics
are using out-of-date PXE rom. Usually the symptoms are that some model
nics will work and some won't.
Also check that spanning tree is not interferring, you may need to disable
it temporarily, lengthen the timeout period, or pause the client for 30
seconds after receiving the ip address.
Make sure a firewall is not blocking port 4011 between your RIS server and
the clients and make sure you include the DHCP server *and* RIS server ip
addresses in the helper address table of your routers (dhcp relays).
Do you have ACLs in place on the client side of the router (VLAN's)? Disable
them for the tests.
--
Scott Baldridge
Windows Server MVP, MCSE
"Gena"
> Thanx
>
> I read this already. But my problem is - RIS is run in AD where there is
not
> any DHCP server and I have a message like:
>
> PXE-E53 No boot file name received
>
> Ater this I tried to use option 66 with IP address of my RIS server and it
> looks like I have to fill options 67 too with name of start boot file. At
> least I've got some another error from TFTP. It looks like one step ahead.
>
> Regards,
> Gennadi
>
> "NIC Student" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Here is a good article Gena:
> >
> >
>
http://www.microsoft.com/windows2000...d_dpl_wnnt.asp
> >
> > --
> > Scott Baldridge
> > Windows Server MVP, MCSE
> >
> >
> > "Gena"
> > > Any idea of file that should be transfered fist after RIS server get
> > request
> > > from PXE card
> > >
> > >
> >
> >
>
>