Network problem with Mandrake 9

Tim

unread,

Dec 15, 2002, 5:18:52 PM12/15/02

to

I'm asking again since I can't get this to work :-(

I have installed Mandrake 9 but I have a major network settings
problem. Using the Mandrake Control Center I can see my network eth0 but
using DHCP the state is always down. If I try to put a static adress the
status is up, but I can not see it in the network anyway. I'm in a LAN
of a provider in Milano.
In my error log I see when using DHCP logs like:
NETDEV WATCHDOG: eth0: transmit timed out
timed out waiting for a valid DHCP server response
Bringing up interface eth0: failed

When I try to give a static address I see errors like:
NETDEV WATCHDOG: eth0: transmit timed out

My network card is a Realtek RTL-8139 and uses the module 8139too.

If I reboot in my windows everything works ok. Can anyone please help me?

Tim

Paul Lutus

unread,

Dec 15, 2002, 5:26:17 PM12/15/02

to

On Sun, 15 Dec 2002 23:18:52 +0100, Tim wrote:

> I'm asking again since I can't get this to work :-(
>
> I have installed Mandrake 9 but I have a major network settings
> problem. Using the Mandrake Control Center I can see my network eth0 but
> using DHCP the state is always down. If I try to put a static adress the
> status is up, but I can not see it in the network anyway. I'm in a LAN
> of a provider in Milano.

Say again? You are hard-wired into your provider's LAN? No dial-up?

You need to provide the details of your networking setup. Your prose
descriptions are not sufficient to even identify the setup.

--
Paul Lutus
http://www.arachnoid.com

Tim

unread,

Dec 15, 2002, 6:08:34 PM12/15/02

to

Paul Lutus wrote:

>
>
> Say again? You are hard-wired into your provider's LAN? No dial-up?
>
> You need to provide the details of your networking setup. Your prose
> descriptions are not sufficient to even identify the setup.
>

I'm connected to a hub in my house provided by my ISP. They have a
DHCP and with windows all works fine, with LINUX no :-(.
Which settings do you need to know?

Tim

Tommi

unread,

Dec 15, 2002, 7:04:16 PM12/15/02

to

Tim wrote:

For a start, run

cat /etc/sysconfig/network-scripts/ifcfg-eth0
and
ifup eth0

and copy-paste their output, and send here

Tim

unread,

Dec 16, 2002, 3:57:03 AM12/16/02

to

cat /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=dhcp
IPADDR=1.50.105.76
NETMASK=255.255.255.0
NETWORK=1.50.105.0
BROADCAST=1.50.105.255
ONBOOT=yes

ifup eth0:
Determining IP information for eth0... failed.

Sybren Stuvel

unread,

Dec 16, 2002, 4:33:56 AM12/16/02

to

In article <UvgL9.34789$t_1.3...@tornado.fastwebnet.it>, Tim wrote:
> cat /etc/sysconfig/network-scripts/ifcfg-eth0:
> DEVICE=eth0
> BOOTPROTO=dhcp
> IPADDR=1.50.105.76
> NETMASK=255.255.255.0
> NETWORK=1.50.105.0
> BROADCAST=1.50.105.255
> ONBOOT=yes

Hmmm... setting both an IP address and using DHCP at the same time looks
a bit weird to me. Also, it sometimes helps to send a certain hostname
in the DHCP request - see the manual of your DHCP client for the options
/ configuration directives. Take a look at your Windows hostname to find
the right name.

Sybren
--
>>> RUNNING A MICROSOFT GAME USING WINE <<<
sybren@sybren:Mechwarrior Mercenaries$ wine MW4Mercs.exe
INSTR_IDT_Emulate Evil attempt to exploit win9x system security flaws detected
INSTR_IDT_Emulate UNIX system security is too strong, can't emulate properly

Tommi

unread,

Dec 16, 2002, 6:31:23 AM12/16/02

to

Tim wrote:

The point of DHCP is that DHCP will send a message "I need IP address" and
DHCP-server will answer by sending ip-address that your eth0 will take.

What you are now doing is first assigning own ip-address, and then using
DHCP to ask ip-address again.

You should remove

IPADDR
NETMASK
NETWORK and
BROADCSAT

from that file.
DHCP will assign all those by itself.