eth0 not working
taharka
res00vl8 at alltel.net
Thu Apr 6 16:43:56 UTC 2006
Howdy,
On Thu, 2006-04-06 at 08:58 -0700, Craig White wrote:
> On Thu, 2006-04-06 at 11:43 -0400, Washington, CJ (OCTO) wrote:
> > Thanks,
> >
> > I don't understand why but when I used the command below, I was logged
> > in as one of the users of the machine and the command failed. Then I
> > logged in as root and reissued the command. It worked fine. I guess
> > you have to be logged in as root in order for the eth0 to work. But I
> > have not tried the same thing using one of the user accounts created
> > on the system.
> >
> > Can someone please explain this?
> >
> > Thanks,
> >
> > C
> >
> > -----Original Message-----
> > From: fedora-list-bounces at redhat.com
> > [mailto:fedora-list-bounces at redhat.com] On Behalf Of Guillermo Garron
> > Sent: Wednesday, April 05, 2006 4:59 PM
> > To: For users of Fedora Core releases
> > Subject: Re: eth0 not working
> >
> > Try
> >
> > /etc/init.d/network restart
> >
> > and what is the output on the screen.
> >
> > regards,
> >
> >
> > Washington, CJ (OCTO) wrote:
> > >
> > > Hello all,
> > >
> > > I just started using Fedora Core 5 and installed it on a Compaq
> > > Deskpro desktop. The install went fine but for some reason, I'm
> > not
> > > able to ping outside of my own IP address. I think that there is
> > an
> > > issue with the eth0 because when I went to shutdown the Kernel,
> > > everything shutdown except the eth0. It hung for hours. Is there
> > > anything special I need to do to get my Ethernet interface on the
> > > Desktop to work with Fedora Core 5? Before this, I was able to use
> > the
> > > port when Windows XP was installed on the machine. Also, when I took
> > a
> > > look at the hardware using the Linux GUI, it stated that the eth0
> > was
> > > enabled and working. Can you please assist?
> > >
> > > CJ Washington
> > >
> > > MPLS Engineer
> > >
> > > OCTO (DCNet)
> > >
> > > CCIE# 4683
> ----
> Please don't post in html
>
> Please don't top post - put your replies on the bottom
>
> /etc/init.d/network restart is a command that requires root privileges.
> Just about any command that operates on underlying hardware/system
> requires root privileges. Users can do user activities.
>
> A user should be able to ping anywhere permitted by routing of the
> network. You might want to log in as a user and try to ping again. In
> fact, you should only log in as a regular user. If you need to obtain
> root privileges in a shell, you would open a terminal window and type
> 'su -' (omitting the quotes) and supply the root password and then you
> would have root privileges.
>
> I don't know why it would have hung while shutting down.
A low quality nic comes to mind when this happens :-(
> Craig
taharka
Lexington, Kentucky U.S.A.
More information about the users
mailing list