At the moment I'm having difficulty getting a thin-client to boot using PXE. Here's the setup:

Server: I have a server running Redhat 9 at 192.168.1.1. It has a D-link DGE-530T card in it.

Client: The thin client is an ancient Pentium-133 with 16 MB RAM and a 3com 3C905CX-TX-M card.

Both the client and server are plugged into a Linksys EG005W gigabit switch.

When I try to boot the client, it fails with a PXE-E51 error: No DHCP or BOOTP offers received. For some reason the client is not "hearing" the DHCP offers broadcast by the server. The following session illustrates the setup for my DHCP server. /var/log/messages shows that the server hears a DHCP request and broadcasts an offer, but the client is not picking it up. I don't think the cabling can be bad since the server hears the request. The communication is working one-way. Why can't the client hear the server? Any help would be greatly appreciated.



[root@kubugam:~]# uname -a
Linux kubugam 2.4.20-8 #1 Thu Mar 13 16:42:56 EST 2003 i586 i586 i386 GNU/Linux

[root@kubugam:~]# tail /var/log/messages
Mar 11 20:35:21 kubugam dhcpd: DHCPDISCOVER from 00:04:75:ad:4d:7c via eth0
Mar 11 20:35:21 kubugam dhcpd: DHCPOFFER on 192.168.1.3 to 00:04:75:ad:4d:7c via eth0
Mar 11 20:35:23 kubugam dhcpd: DHCPDISCOVER from 00:04:75:ad:4d:7c via eth0
Mar 11 20:35:23 kubugam dhcpd: DHCPOFFER on 192.168.1.3 to 00:04:75:ad:4d:7c via eth0
Mar 11 20:35:27 kubugam dhcpd: DHCPDISCOVER from 00:04:75:ad:4d:7c via eth0
Mar 11 20:35:27 kubugam dhcpd: DHCPOFFER on 192.168.1.3 to 00:04:75:ad:4d:7c via eth0
Mar 11 20:35:35 kubugam dhcpd: DHCPDISCOVER from 00:04:75:ad:4d:7c via eth0
Mar 11 20:35:35 kubugam dhcpd: DHCPOFFER on 192.168.1.3 to 00:04:75:ad:4d:7c via eth0
Mar 11 20:47:35 kubugam sshd(pam_unix)[30450]: session opened for user cwh by (uid=500)
Mar 11 20:47:43 kubugam su(pam_unix)[30486]: session opened for user root by cwh(uid=500)

[root@kubugam:~]# cat /etc/dhcpd.conf
ddns-update-style ad-hoc;

subnet 192.168.1.0 netmask 255.255.255.0 {

}

host pxeclient {
hardware ethernet 00:04:75:ad:4d:7c;
fixed-address 192.168.1.3;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
filename "pxelinux.0";
}

[root@kubugam:~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:3D:F0:B8:BC
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7362 errors:0 dropped:0 overruns:0 frame:0
TX packets:7362 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:646220 (631.0 Kb) TX bytes:646220 (631.0 Kb)

[root@kubugam:~]# netstat -anp | egrep -w 67
udp 0 0 0.0.0.0:67 0.0.0.0:* 16445/dhcpd

Hi,

try this link, perhaps u will get the clue.

http://www.quepublishing.com/article...&seqNum=1&rl=1


thanks

Thanks, but no thanks. I fail to see the connection between my problem and installing Fedora Core 3.

Hi there, try to use my dhcpd.conf and see if it works. Change the hosts and server ip to suite u.:
NOTE: Pls make sure that, the /tftpboot is your "/" directory. So all ur files such as "pxelinux.0", kernel image, ramdisk and "pxelinux.cfg" folder should be there.