Client Fails to Connect With DHCP/BOOTP Server

If you have installed or added a new client, but the machine fails to connect to the server and displays an error message, check the machine's cable and adapter. If the adapter has a diagnostic program, run it to identify possible problems.

Start the Configuration application in the PCNFSpro directory. Choose Services and enable the Start Network Event Log. You can also start the Network Event Log directly from its icon. After it starts, choose Display and then Configure. Select all priority levels, down to Debug. Choose Save to save the configuration. Network Event Log entries similar to:

DHCP: Attempting to configure interface using DHCP

indicate that the machine has broadcast for a configuration. Server replies should follow.

Next, kill the in.dhcpd daemon on the server and run the server in diagnostic mode by entering in.dhcp -d.

After receiving output, check that there is a DHCP server or relay agent on the machine's subnet. While booting the client, run:

snoop udp port 67 or udp port 68

on a server on the same subnet as the machine. See if a system responds. Windows client snoop output looks like this:

OLD-BROADCAST -> BROADCAST UDP D=67 S=68 LEN=311

glrr -> BROADCAST UDP D=68 S=67 LEN=490

The client name is not shown for the Windows client. The DHCP activity is reflected by the presence of BROADCAST.