Static IP Ethernet Problems in Mandrake 8.x

Posted on 2002-05-19
Last Modified: 2013-12-15
Hi, my computer has been setup with both windows 2000 and mandrake 8.1.  Before I was using both with dhcp ethernet and it was working just fine.  But I moved to an apartment where I have a static ip address.  I was able to get the windows networking working with the new ip info. I was given.  But the linux networking doens't seem to be working on static ip.  :-(  

I thought it might be a problem with Mandrake 8.1, so I formatted the linux partition and installed Mandrake 8.2.  And I entered the static ip info when I went through the setup.  I don't know what I'm doing wrong.  I entered the exact same ip, dns, gateway, and netmask into the windows networking configuration, and it works just fine.  

Can someone please help me out?


Question by:jenny_holmes1980
  • 3
  • 2
LVL 17

Expert Comment

ID: 7019589
Are you sure your eth0 get initialized OK?
Post output of ifconfig eth0.
What make and model LAN card?

Author Comment

ID: 7020360
Okay, I'm not sure if my eth0 is being initialized properly.  It seems like it is because it says that the status of the lan is "up" within the mandrake control center.  And it also says "ok" when it tries to bring it up during boot.  However, when I try to get it to connect to the internet, it never works.  

Here is my ethernet info:
subnet mask:
default gateway:
preferred dns:
alternate dns:

And that works in windows 2000.

Here is my /etc/sysconfig/network file:


And here is my /etc/sysconfig/network-scripts/ifcfg-eth0 file:


My lan card is a 3Com EtherLink 10/100 PCI TX NIC (3C905B-TX).  I think that mandrake recognizes it without any problems.  Well, I'm coming to that conclusion because I was always able to use this card with dhcp ethernet (in mandrake and windows) without any problems.

Please give me any suggestions you have.

thanks so much,

jenny :-)
LVL 40

Expert Comment

ID: 7020706
Given the data above it would look like basic networking is configured properly. I can't tell if your DNS is set up properly from that but /etc/resolv.conf should contain something like:


Right now I'd guess that resolv.conf isn't right and that's the problem. But, to be sure that the configuration is correct you can look at the output of 'ifconfig eth0' and you should see:

eth0      Link encap:Ethernet  HWaddr 00:01:02:35:CB:FE  
          inet addr: Bcast: Mask:
          RX packets:16818955 errors:1 dropped:0 overruns:1 frame:2
          TX packets:3251391 errors:0 dropped:0 overruns:0 carrier:1
          collisions:379 txqueuelen:100
          RX bytes:2210443508 (2108.0 Mb)  TX bytes:207584086 (197.9 Mb)
          Interrupt:11 Base address:0xe400

There should not be an excessive number of errors, dropped, or overruns, nor should the collisions be a large number relative to the TX packet count.

And there should be a line in the output of "netstat -rn" like:         UG       40 0          0 eth0

If that matches what you see you should have basic connectivity and you can verify that by trying a ping of your gateway, like:

chaos> ping -c 3
PING ( from : 56(84) bytes of data.
64 bytes from icmp_seq=0 ttl=238 time=45.944 msec
64 bytes from icmp_seq=1 ttl=238 time=46.875 msec
64 bytes from icmp_seq=2 ttl=238 time=45.360 msec

--- ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/mdev = 45.360/46.059/46.875/0.671 ms

Then verify that your DNS is working by trying a lookup like:

chaos> host domain name pointer

If one of those doesn't work I can probably tell what's wrong from knowing which failed.

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.


Author Comment

ID: 7020787
Hi again,

Okay, I tried doing that, here's what I found.

My /etc/resolv.conf originally had just:

search localdomain

I changed it to the following:


Next I tried 'ifconfig eth0', here's the output of that:

[root@localhost network-scripts]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:DA:0A:50:2B  
          inet addr:  Bcast:  Mask:
          RX packets:2159 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:355013 (346.6 Kb)  TX bytes:480 (480.0 b)
          Interrupt:11 Base address:0xe000

Then I did 'netstat -rn', and here's that output:

[root@localhost network-scripts]# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface   U        40 0          0 eth0       U        40 0          0 lo

I assumed that the ping and dns wouldn't work, but I tried them anyway, here are their outputs:

[root@localhost sysconfig]# ping -c 3
connect: Network is unreachable

[root@localhost sysconfig]# host
;; connection timed out; no servers could be reached

I hope you know what's wrong.  The problem's been out of my reach for some time now.

thanks so much again,

LVL 40

Accepted Solution

jlevie earned 75 total points
ID: 7020826
Okay... Now that I see what's happening I can see that there's something that I overlooked in your network config data. According to what you said earlier your config data is:

subnet mask:
default gateway:

There's a problem here in that the default gateway lies outside of the network that your system is in. According to that config data your system in in the network. But the gateway is in the network if the netmask is right. So as far as Linux is concerned there's no way to reach the default gateway as its IP lies in a different network. That's why there's no default route showing in the output of netstat. That would say to me that either you have the wrong IP for the gateway, the wrong netmask or the wrong IP for your system.

You say that w2k works. Take a look at the output of 'ipconfig /all' when executed in a cmd window and compare the IP, netmask, and gateway to the config data you are using on the Linux system. I think you are ging to find something is different.

Author Comment

ID: 7020862
Wow, I can't believe how something that small could
have caused the entire problem.  Thank-you so much.

So I did 'ipconfig /all' in windows, and it just showed
me what I had entered for the config myself.  So, I booted
into linux and changed the gateway to  It
connected me to the internet in seconds.



Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Daily system administration tasks often require administrators to connect remote systems. But allowing these remote systems to accept passwords makes these systems vulnerable to the risk of brute-force password guessing attacks. Furthermore there ar…
rdate is a Linux command and the network time protocol for immediate date and time setup from another machine. The clocks are synchronized by entering rdate with the -s switch (command without switch just checks the time but does not set anything). …
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:

789 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question