interface eth0 failure - RH enterprise WS

I have a working Debian machine in which I replaced the HD with a new HD
and loaded a copy of RH Enterprise WS 3 academic (that I just purchased from
RH for $25).



Everything went well during the install (I used downloaded ISO's that I
checksummed) until it got the "bringing up interface eth0". I had forgotten
to plug in the ethernet cable from my cablemodem/router (DHCP) so it failed.



I thought: no problem, shutdown, pulled the NIC , rebooted, used Kudzu to
remove the NIC, shutdown again, reinstalled the NIC, Kudzu found the NIC but
still encountered the long pause and failure at "bringing up interface
eth0".



I've, tried removing and reinstalling the NIC several times since and
tested the NIC on another machine to re-confirm that it works and it does.
So it seems it's a RH problem.



Not sure if my initial failure to plug the CAT5 cable in initially, affected
things but I can't see why it would in the long run.



If anyone knows what the problem is or how I can fix it, I would very much
appreciate the help. I'm stumped.



No RH phone support with my academic license and I am a RH newbie...




DMS

DMS wrote:
>
> Everything went well during the install (I used downloaded ISO's that I
> checksummed) until it got the "bringing up interface eth0". I had forgotten
> to plug in the ethernet cable from my cablemodem/router (DHCP) so it failed.
>
>
>
> I thought: no problem, shutdown, pulled the NIC , rebooted, used Kudzu to
> remove the NIC, shutdown again, reinstalled the NIC, Kudzu found the NIC but
> still encountered the long pause and failure at "bringing up interface
> eth0".
>

Why'd you do this? Simply plugging the cable in and restarting the
network would've solved the problem no matter what the distribution.
Have you tried doing an manual insmod and manual restarting of the
network? All the skills you've used with Debian should transfer over,
only the locations of files and some of the installed tools are probably
what has really changed.

>
>
> I've, tried removing and reinstalling the NIC several times since and
> tested the NIC on another machine to re-confirm that it works and it does.
> So it seems it's a RH problem.
>
>
>
> Not sure if my initial failure to plug the CAT5 cable in initially, affected
> things but I can't see why it would in the long run.
>
>
>
> If anyone knows what the problem is or how I can fix it, I would very much
> appreciate the help. I'm stumped.
>
>
>
> No RH phone support with my academic license and I am a RH newbie...
>
>

DMS wrote:
> I have a working Debian machine in which I replaced the HD with a new HD
> and loaded a copy of RH Enterprise WS 3 academic (that I just purchased from
> RH for $25).
>
>
>
> Everything went well during the install (I used downloaded ISO's that I
> checksummed) until it got the "bringing up interface eth0". I had forgotten
> to plug in the ethernet cable from my cablemodem/router (DHCP) so it failed.
>
>
>
> I thought: no problem, shutdown, pulled the NIC , rebooted, used Kudzu to
> remove the NIC, shutdown again, reinstalled the NIC, Kudzu found the NIC but
> still encountered the long pause and failure at "bringing up interface
> eth0".
>
>
>
> I've, tried removing and reinstalling the NIC several times since and
> tested the NIC on another machine to re-confirm that it works and it does.
> So it seems it's a RH problem.
>
>
>
> Not sure if my initial failure to plug the CAT5 cable in initially, affected
> things but I can't see why it would in the long run.
>
>
>
> If anyone knows what the problem is or how I can fix it, I would very much
> appreciate the help. I'm stumped.
>
>
>
> No RH phone support with my academic license and I am a RH newbie...
>
>
Are you able to see the interface after it boots up (using ifconfig -a)?
If so then at least the module loaded ok.

If you can see the interface, check the configuration of the interface
in /etc/sysconfig/network-scripts/ifcfg-eth0. Is the BOOTPROTO variable
set to dhcp?

If thats set, try to run:
ifup eth0
if it fails again, check /var/log/messages for any debugging output.

HTH
Neil

--
Neil Horman
Red Hat, Inc., http://people.redhat.com/nhorman
gpg keyid: 1024D / 0x92A74FA1, http://www.keyserver.net