I'm brand new to Linux. I built my first Linux box w/RH 8.0 this week, and I'm having difficulties with the IP stack. DHCP does not seem to work, and assigning a static address gets me nothing either. I've checked the module for the NIC and it seems to be ok. I can ping the box itself when assigned statically, but when I ping anything else, I get "destination unreachable." I've checked and double checked address, sm, and gateway to no avail. Anybody have any suggestions? Thanks for the help.

'DHCP does not seem to work'
where? at your linux box or ISP? if you mean your linux box - you can check if it is running typing 'ps -A'

'I can ping the box itself when assigned statically'
which way? using numeric ip address or dns name?

'I get "destination unreachable."'
if you try to ping with command like 'ping 1.2.3.4' (numerical ip) the reason is probably improper gateway definition (check it using 'route') but if you try ping using the host name check /etc/resolv.conf file - shoud have a 'nameserver x.x.x.x' definition , where x.x.x.x is numerical ip of DNS server

The Linux client will not obtain an IP address from my DHCP server.

I can ping the Linux box (from itself) by both address and hostname.

As I watch the loader, it claims that no link is present and to check the cable, however I've verified that this cable is good. As a result, I have to bring up the interface manually.

I've discovered however, that if I bring the interface up manually and the use dhclient, it will obtain and address.

Any ideas?

Thanks.

Well, I do not know what to do. The only case I met the information about link state was concerned with tulip card. But I've replaced this card with Realtek (a lot of troubles) so I can up my eth at any moment with or without phisical connection to the network. I really do not understand the idea of NIC drivers which take care about 'live' link at the moment of upping the interface.
So, sorry. Maybe somebody elso recognise the problem. Hope, after manual dhclient run everything works correctly (?).

A quick workaround may be to create a script to initiate the device at the end of the boot rather than in the middle.