Hello,

Having a problem configuring a Compaq Deskpro PC running RH 7.0 (no patches or anything) as a DHCP client on my corporate LAN. I go into netcfg (I did give my system a fully-qualified hostname here, not sure if this is relevant), select "eth0" & select "dhcp" as the interface protocol. I save my work and try to activate eth0 and I see the message "delaying eth0 initialization" in my terminal window. Same results when I use "linuxconf". Multiple reboots fail to bring the interface up. dhcpcd also fails to start when I try to start it manually.

I don't have a static IP yet (hence the reason for me trying to get dhcp working) so I haven't tested if the NIC works with a static IP, but I AM able to successfully ping localhost without incident.

I am getting my dns info./primary default gateway/dhcp server info. from my Windows 2000 workstation (ipconfig /all), which is using DHCP without a problem.

I notice that when I configure DHCP on a Tru64 UNIX Alpha workstation (using "sysman network"), one of the things it prompts me for is a DHCP server name; I am missing something on RH because I don't see where I enter the DHCP server information in netcfg/linuxconf.

Pilot error on my part? Wouldn't be surprised. Any thoughts/suggestions/pointers are greatly appreciated.

you dont have to give a dhcp server name for linux. who runs the dhcp server? is it behind a firewall?

please post the results of 'ifconfig'

and the contents of '/etc/sysconfig/network-scripts/ifcfg-eth0'

you can look in '/var/log/messages' for the error messages when it is trying to get the ip

Thanks for the quick response.

>you dont have to give a dhcp server name for linux.

Ok, thanks.

>Who runs the dhcp server?
>Is it behind a firewall?

Don't know. I am not in the office today,
but will check this tomorrow and post results.

>please post the results of 'ifconfig'

This only reports lo0 info.; eth0 doesn't show up at all.
At some point I removed eth0 and now I actually have eth1
that I configured in netcfg (which also doesn't show up in
ifconfig output). Still able to ping localhost, though.

Suspected NIC problem originally, need to look at this
more closely it seems.

>..and the contents of
>'/etc/sysconfig/network-scripts/ifcfg-eth0'

Will post here when I am in the office.

>you can look in '/var/log/messages' for the
>error messages when it is trying to get the ip

Will check this as well.

Thanks again.

I don't think I was clear on something:
============================

>I am getting my dns info./primary default gateway
>/dhcp server info. from my Windows 2000 workstation
>(ipconfig /all), which is using DHCP without a problem.

What I mean here is that my W2k system is a dhcp client on our corporate LAN and I am "filling in the blanks" on the linux system from the info. on the W2K system. However, it doesn't appear that I need to be doing this; dhcp SHOULD fill in the blanks for me(i.e. assign/lease me an IP address-->dns info-->primary default gateway) after I set up the NIC to be a dhcp client in netcfg or linuxconf, so this looks like it might be pilot error after all.

Time to study some more, but replies are still welcome and appreciated.

If the W2K workstation is up and getting DHCP, and /etc/sysconfig/network-scripts/ifcfg-eth0 has a line that says
BOOTPROTO=dhcp
and the dhcpcd package is installed (verify this with 'rpm -q dhcpcd'), you should be in business.

Problem solved

The system I am using has an Embedded Intel PRO/100+ Management Adapter in it, which wasn't compiled in the kernel.
I thought I could upgrade from RH 7.0 to 7.1 to get the network driver support I needed, but it didn't work.

I performed the necessary kernel build steps (slightly revised for my configuration, per the URL below) to add this NIC to my kernel:

http://www.redhat.com/docs/manuals/l...dularized.html

At any rate, I am at 7.1 and I am on the network so I am happy.

Thanks for all of the replies and suggestions.