I have been trouble by this problem for a very long time already.

I connect my Host RH7.3 PC to a target board.
When I do a boot up, it shows :

Searching for Server (BOOTP/DHCP)
<sleep>
<sleep>
....
....
<sleep>

Here is the status of my Host PC:
# rpm -qa | grep dhcp
dhcp -2.0pl5

# /etc/rc.d/init.d/dhcpd start [OK]
# /etc/rc.d/init.d/nfs start [OK]
# /etc/rc.d/init.d/nfslock start [OK]

# ifconfig -a
eth0 ...
inet addr: 192.168.0.71 Bcast: 192.168.0.255 Mask: 255.255.255.0
....

# emacs /etc/dhcpd.conf
...
...
.... subnet-mask 255.255.255.0;
.... broadcast-address 192.168.0.255;
.... routers 192.168.0.254;
... domain-name-servers 192.168.0.?;
... domain-name "localdomain";

host xxx {
hardware ethernet xx:xx:xx:xx:xx; <- My target board MAC
fixed-address 192.168.0.111; <- I give target board IP addr
.... option-128 "DODES"; <- What is DODES??
..... option-129 "console=ttySC0,115000 ether=xx xxxxxx";
}

Here is the status of my target board:
# ifcfg-eth0
NETWORKING=yes
BOOTPROTO=dhcp
ONBOOT=yes


Is there anything wrong with my configuration or IP setting??
The more I do, the more I get confused as my Server (BOOTP/DHCP) is still
<sleep> <sleep> <sleep> .....

Could anyone please offer me any help or advises on this???
I really need any kind of little help!!!

Greatly appreciate it! Thank you a zillom times in advance!!

What OS is the target board running, or is this message from a boot ROM (if so, is it doing PXE?) ?

Sincerely

Bill Jennings

It is a hitachi chip with Sh-linux 2.4.26.
The user manual is in Japanese word because I order it from Japan.

I am not very sure on the OS of this target board. It should
be redhat.

Could you help me on this 'bothering' problem??
Thank you!!

Can you run the following command while the target board is trying to boot:

tcpdump port 67 or port 68

and post the outuput?

This will help us to see what (if anything) is happening on the wire.

Sincerely
Bill Jennings

Ok, give me a sec cause I have just reinstalled my RH7.3 in my host PC. I will post it once I type it.

Sorry to have keep you waiting.
Please do help me.
Thank you very much!!

Hi, here is some information I want to share it with you all.

# /etc/rc.d/init.d/dhcpd stop
# /usr/sbin/dhcpd -d

Internet Software Consortium DHCP Server 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

Listening on Socket/eth0/192.168.0.0
Sending on Socket /eth0/192.168.0.0
DHCPDISCOVER from 00:10:0c:00:14:5e via eth0
DHCPOFFER on 192.168.0.111 to 00:10:0c:00:14:5e via eth0
DHCPDISCOVER from 00:10:0c:00:14:5e via eth0
DHCPOFFER on 192.168.0.111 to 00:10:0c:00:14:5e via eth0
DHCPDISCOVER from 00:10:0c:00:14:5e via eth0
DHCPOFFER on 192.168.0.111 to 00:10:0c:00:14:5e via eth0
...
...
...
DHCPDISCOVER from 00:10:0c:00:14:5e via eth0
DHCPOFFER on 192.168.0.111 to 00:10:0c:00:14:5e via eth0

tcpdump: command not found

You must be root to run tcpdump. It is not in the PATH for normal users. Also, you may not have it installed.

But...

Given the output of the dhcp daemon you posted above, I'd say your ethernet wire is bad. The transmit side of the target board is getting to the receive side of the linux box (the dhcp server can hear the target's requests: DHCPDISCOVER) but the transmit side of the linux box is not getting to the receive side of the target board (the target board cannot hear the linux box's reply: DHCPOFFER).

Do you see the link light on both ethernet connectors when you plug in the crossover cable?

How is the crossover cable wired?

Here is how I believe it should be wired:

1 <-> 3
2 <-> 6
3 <-> 1
4 < not used > 8 (these pins are not used for CAT 5e and may be left open)
5 < not used > 7 (these pins are not used for CAT 5e and may be left open)
6 <-> 2
7 < not used > 5 (these pins are not used for CAT 5e and may be left open)
8 < not used > 4 (these pins are not used for CAT 5e and may be left open)

Hope this helps.

Bill Jennings

Actually I make the cross cable myself. I have just check it
1<->3
2<->6
3<->1

I use this cable and connect my RH7.3 PC to my window PC.
Statically set the IP and ping to each other. It works.
So I guess it is not the cable problem.

Actually when I connect my target board to the window PC
and did a etherboot. It gives the same error message:

...Searching for Server (BOOTP/DHCP)
<sleep>
<sleep>
....
<sleep>




I have been reinstalling and reconfiguring my linux PC dozens of times already. I am going nuts soon.
Please help!!

Well, there you go! You left out one wire:

6<->2

You listed only three wires. It takes four wires to make an ethernet connection.

Sincerely
Bill Jennings

Cool!!! I am gonna re-do my cable. Let you know the result again.
Please come back here again tomorrow.

Thank you thank you thank you so much!!!!! I am so grateful to your kind help!! Oh my gosh!! I finally solve this 'silly' problem.
HOw can I thanks you!!! I have been struggling this for weeks!!
I thought its my host PC configuration that is giving me the problem.

Once again, THANKS A ZILLOM!!!

Hello,

I am back with the same problem again. :"()

Waiting for completion of auto negotiation (5sec) ...... Done.
Searching for server (BOOTP/DHCP)...
<sleep>
<sleep>
<sleep>

This time, I am sure that my ethernet cable is the correct one coz I have
been using this for a long time and so such problem till I did something.
I do not know what I have changed.

Could anyone please help??
I am suspecting my hosts or dhcpd.conf files. I am not sure.

Could some one please help??