Let me start off by filling in some background. I have 4 network linux servers that are running Cent Os 4.3. One of which is messed up. None of the servers have a CD rom so network boot is basically the only option. I myself know nothing about linux (Taking crash course now and plan to install ubuntu on a personal machine to learn it as well). I am taking this oppurtunity to fresh install Cent OS and partition the HD to dual boot windows 64 bit to use a test bed for our software. I must apologize for the lenth of this post.

Here is what I have done so far.

The TFTP server part:

# mkdir /tftpboot
# chown nobody:nobody /tftpboot

service tftp
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -c -s /tftpboot
disable = no
per_source = 11
cps = 100 2

/etc/rc.d/init.d/xinetd reload
This was OKed by linux

the DHCP part:

ddns-update-style ad-hoc;
option domain-name "hyper.com";
option domain-name-servers centos2.hyper.com;
option subnet-mask;
allow booting;
default-lease-time 600;
max-lease-time 7200;
server-name "centos2";

subnet netmask {
option routers;

host tftpclient {
hardware ethernet 00:30:18:A6:33:5E; #machine needing booting
filename "/tftpboot/boot/centos4.3";

/etc/rc.d/init.d/dhcpd start
This was OKed by linux as well.

The disk image:
mkdir /tmp/c4
mount -o loop -t iso9660 boot.iso /tmp/c4
cd /tmp/c4
mkdir /boot/centos4.3
cp -r -v * /boot/centos4.3
umount /tmp/c4
This was OKed by linux as well.

I go through the bios on the machine needing reinstall and set it up to boot off the LAN network. It detects the DHCP server but stalls at the TFTP server and then tells me bad boot disk. After about 30 minutes. What did I miss or mess up? Everything seems to be ok with servers I have done. Again I am a linux n00b so I dont know much about it. After I get this running I will need to research how to format and how to properly set up partitions for linux and windows so that I may dual boot it.