Stuck on TFTP Problem, I Think???

I have been working on this the 6 Days now and still no luck. I have search for hours and hours and tried over 200 different example \ suggestion and configurations(I have made note of every change). I have just about lost all faith in all examples. Maybe this is down to SUSE 7.3.

Please anyone, Do you now how to get suse 7.3 working with remote boot. It should not be this hard!!!

I am trying to boot a dos machine using pxe and receiving the error:

PXE-E32: TFTP open timeout

Setup:
Suse Linux 7.3
3Com 3C905-tx-m network card with: PXE Rom V2.00
tftp-hda 0.32
ISC dhcp server V3.0

# dhcpd.conf
#

ddns-update-style none;

authoritative;

option option-135 code 135 = text;
option option-155 code 155 = text;
option dhcp-class-identifier code 156 = text;

option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;

ddns-update-style ad-hoc;
option broadcast-address 192.168.0.255;
option domain-name-servers 192.168.0.12;
option routers 192.168.0.12;

subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.14 192.168.0.30;}

allow booting;
allow bootp;

host test1 {
hardware ethernet 00:04:75:8c:28:52;
fixed-address 192.168.0.28;
next-server 192.168.0.2;
option option-135 "-i";
# option option-135 "start";
option vendor-class-identifier "PXEClient";
option vendor-encapsulated-options 01:04:00:00:00:00:ff;
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
filename "bpbatch";

}

tcpdump:
23:24:18.980229 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x768c2852 secs:1024 flags:0x8000 [|bootp]
23:24:18.980892 linux.local.bootps > 255.255.255.255.bootpc: xid:0x768c2852 secs:1024 flags:0x8000 Y:192.168.0.28 S:linux.local ether 0:4:75:8c:28:52 [|bootp] [tos 0x10]
23:24:19.966029 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x768c2852 secs:1024 flags:0x8000 [|bootp]
23:24:19.966910 linux.local.bootps > 255.255.255.255.bootpc: xid:0x768c2852 secs:1024 flags:0x8000 Y:192.168.0.28 S:linux.local ether 0:4:75:8c:28:52 [|bootp] [tos 0x10]
23:24:19.976975 arp who-has linux.local tell 192.168.0.28
23:24:19.977029 arp reply linux.local is-at 0:4:75:8b:f1:6e
23:24:19.977227 192.168.0.28.2070 > linux.local.tftp: 24 RRQ "bpbatch"
23:24:19.977348 linux.local > 192.168.0.28: icmp: linux.local udp port tftp unreachable [tos 0xc0]

dchp works fine and client obtains an ip address.

From reading this file, the problem seems to be related to tftp being unreachable.
My tftp directory is /tftpboot on the root. and contains bpbatch bpbatch.ovl and bpbatch.hlp

inetd.conf contains

tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
bootps dgram udp wait root /usr/sbin/bootpd bootpd -c /tftpboot

Many thanks
Ian

To get tftp to work not only do you set up the dhcp server to send the right pxe info out (PXE pronounced pixie, I always thought that was such a wimpy name) but you need to set up a tftp server. Sounds like you have the tftp port open on your system based on your inetd.conf but you also need an actual server that answers the tftp requests. I've done it on a windows box where tftp server is built into the PXE software package but in linux you set it up seperatly. I belive you can get most ftp servers configured to handle tftp (bootp) requests but don't know about the specifics. It's probably in the docs you used to set up DHCP to work though.

Hope that helps.