Prev: XEN <-> VMWare
Next: Reverse Print Order
From: Pink on 22 Mar 2007 05:42
Bit of a strange one.

This is with Redhat EL4 WS on an HP xw9400.


I plugged this box in our network and it worked fine on eth0 using
dhcp. I took the box to the client and plugged it in to their network
and eth0 fails on boot with .


"Bringing up interface eth0:" "Determining IP information for eth0...
failed; no link present. Check cable?"


Running dhclient on eth0 gives multiple DHCPDISCOVER messages and
fails to return any DHCPOFFERS.


I checked the gnome network tools and it said the interface was bound
to a mac address so I removed the binding and attempted to use
dhclient to assign an address again with exactly the same result as
above.


However if I plug into the eth1 interface DHCP is fine. This
indicates
to me (because both interfaces are identical) that this is a
configuration problem and something has locked out the interface.


I don't have access to the box at the moment, but I need to find out
why this is behaving in this manner.


Does anyone have any ideas that I can try next time I go on site?

From: Dan Espen on 22 Mar 2007 09:15
"Pink" <peaeyeennkay(a)googlemail.com> writes:

> Bit of a strange one.
>
> This is with Redhat EL4 WS on an HP xw9400.
>
>
> I plugged this box in our network and it worked fine on eth0 using
> dhcp. I took the box to the client and plugged it in to their network
> and eth0 fails on boot with .
>
>
> "Bringing up interface eth0:" "Determining IP information for eth0...
> failed; no link present. Check cable?"

Try Google searches for that message.
At least one hit suggests kudzu is the problem.
From: Pink on 27 Mar 2007 06:31
On Mar 22, 2:15 pm, Dan Espen <dan...(a)MORE.mk.SPAMtelcordia.com>
wrote:
> "Pink" <peaeyeenn...(a)googlemail.com> writes:
> > Bit of a strange one.
>
> > This is with Redhat EL4 WS on an HP xw9400.
>
> > I plugged this box in our network and it worked fine on eth0 using
> > dhcp. I took the box to the client and plugged it in to their network
> > and eth0 fails on boot with .
>
> > "Bringing up interface eth0:" "Determining IP information for eth0...
> > failed; no link present. Check cable?"
>
> Try Google searches for that message.
> At least one hit suggests kudzu is the problem.

Thanks for the reply.

I have tried repeated searches on google already for possible reasons
as to why. Though I must admit to including "redhat" "EL4" "RHEL4"
"xW9400" and such like in the queries.

A generic search for the error message brings up a lot of noise so I
was hoping for something more distribution specific.

I am now trying to track down the result you mentioned and hoping it
may shed some light on the issue.

Once again thanks for the reply.

 | 
Pages: 1
Prev: XEN <-> VMWare
Next: Reverse Print Order