[syslinux] Has anyone any insight as to why RedHatEnterprise Level 5 is broken as far as PXE booting is concerned.

[Dyks, Axel (XL)]

RgSalisbury wrote:
> OK
> 
> Different symptons
> I have now tried on a RHEL different machine with a different nic.(Intel 
> ethernet pro 100)
> But same client & a different client
> 
> Client messages are:
> 
> ##################
> PXE-T02  Only absolute filenames allowed
> PXE-E3C  TFTP ERROR - Access Violation
> PXE-M0F: Exiting Broadcom PXE ROM.
> ##################
> ##################
> PXE-T02  Only absolute filenames allowed
> PXE-E3C  TFTP ERROR - Access Violation
> PXE-M0F: Exiting Intel PXE ROM.
> ##################
> Added
> next-server
> 
> to My minimal dhcpd.conf & looks thus:
> ##################
> ddns-update-style interim;
> ignore client-updates;
> subnet 172.16.0.0 netmask 255.255.255.0 {
>       option routers                 172.16.0.254;
>       option subnet-mask       255.255.255.0;
> host abcd  {hardware ethernet 00:01:6c:ca:24:7b ;fixed-address 172.16.0.30;}
> filename "pxelinux.0";
> allow booting;
> allow bootp;
>       range dynamic-bootp 172.16.0.128 172.16.0.254;
>       default-lease-time 21600;
>       max-lease-time 43200;
>       host ns {
>             next-server 172.16.0.254;
>             hardware ethernet 00:02:B3:99:05:A0;
> # 00:02:B3:99:05:A0 is MAC  on the dhcpd & tftp server box
>             fixed-address 172.16.0.254;
>       }
> }

fixed-address 172.16.0.254 ???

Seems that you are trying to assign the dhcp server's ip address
also to the client.

Furthermore "hardware ethernet ..." should list the CLIENT'S
MAC address and not the server's, if you want to assign
a fixed IP address to the client.