Ethernet/Fire wall settings not working - EASY FIX

[Walter David III <walter david verizon net>]

Did you do a complete install or just a workstation install..
Just curious?  For the last 6 months this list has had the ever
ongoing question about how to get the eithernet working in
redhat 8..   After about 10 installs on about 4 different computers
doing a complete install..and server installs..
I finally figured out that the firewall setting only stick during set up
if you do a workstation install or a home office install...
The problem there is that you can set up file sharing or anything
via samba..  so do a workstation or home office install with your
firewall settings OFF or Custom and check everything including
trusted device ETH0 and install ..  then after installed you should
then from root be able to activate you eithernet card interface..
then install everything else you need from the c.d. after the card is 
running...
like samba ..windows file sharing...blah ..blah...blah...
This is the only way I got the eithernet card to activate.
I think that most people probably can't understand why some of us
can't get our machines to activate the DHCP via EthO.. but thats 
probably
because there all doing workstation installs and everything is just 
working
when they boot into X windows..  I think its just server and full 
install
people having all the Eithernet card problems...but thats just a guess,
I be interested to know if thats true..
hope this helps somebody...

Walter  David




On Tuesday, November 26, 2002, at 02:36  PM, Tom Panton wrote:

> The message that displays upon boot is the following:
>
> "Determining IP info for eth0...failed"
>
> And it puts a red "failed" in the brackets instead of "[ok]" to eth0.
>
> -Tom
>
>
> on 11/26/02 1:28 PM, Bob McClure Jr at robertmcclure earthlink net 
> wrote:
>
> > On Tue, Nov 26, 2002 at 01:18:21PM -0600, Tom Panton wrote:
> > > /etc/sysconfig/network-scripts/ifcfg-eth0 parameters:
> > >
> > > USERCTL=no
> > > PEERDNS=yes
> > > TYPE=Ethernet
> > > DEVICE=eth0
> > > HWADDR=00:c0:4f:38:4e:46
> > > BOOTPROTO=dhcp
> > > ONBOOT=yes
> >
> > Hmm.  I'm on a static setup, not DHCP.  Could there be some disconnect
> > with the DHCP server?
> >
> > Again, what about messages during boot?
> >
> > Cheers,