I've installed Fedora core 5 in a pc with 3 network cards. I've assigned them their static ip, and netmasks and gateway and none of those 3 cards can ping the gateway. Exactly as if the network cables are cut. So the ping from within the machine works perfect, but not link with the outside is registered.

Obviously I've exchanged wires with functioning machines. I've connected a windows machine with the same ip configuration and it worked without problem. I've used the same cables, the same switch and the same ip's on the windows box (my laptop).
Everything is allright, except that for the fedora installation network is not reached.

What should I check to begin catching the problem?

Thank you,

Alejandro

what does a 'ifconfig' show? what does a 'netstat -rn' show?

With that info I can provide you with further assistance :-)

-Scott

Thank you very much scott.
I have 3 servers in a datacenter and the number 1 and number 2 work perfectly. The number 3 is the problematic one.

I am almost lost with this problem. I asked some linux gurus and they worket a couple of hours and finnaly they gave up. They told me that they have set private ips to the machines conected to the switch (servers 1,2 and 3) and that this machine (server 3) is not able to communicate with others on the same switch. They said that the problem may be due to some very strange problem on the PCI bus of the mother.
The mother is an A8VMX, and the processor is an AMD 64bit.
I've installed a fedora 5 distro, 64 bit ready.
This linux gurus also changed network cards (they tried 4 in total), exchanged cables with the other servers on the same switch, and the network still didn't work on server 3. Finally they installed a knoppix distro and everything worked in a minute, except the network, that still refused to work.
His advice was to install a windows os and see if it works, and I am going to do this tomorrow. If the windows os works, they promised to resing and dedicate to sell hot-dogs.

After taking a look at netstat -rn on this server number 3 I've got something like (I've took a picture at the screen but I can recheck tomorrow):

[root@s3 /]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
200.111.130.0 " 255.255.255.0 U 0 0 0 eth0


whereas the server number 2 reads (I've checked a minute ago):


[root@s2 /]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
200.111.130.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 200.111.130.1 0.0.0.0 UG 0 0 0 eth0

The server s3 has the following ifconfig (from another picture):

[root@s3 /]# ifconfig eth0
Link encap: Ethernet NWaddr 00:15:F2:C1:EB:E8
inet addr: 200.111.130.4 Bcast: 200.111.130.255 Mask:255.255.255.0
BROADCAST MULTICAST MTV:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 base address:0xc400


Any idea?
Alejandro

You need to add a default route to s3 the command for you would be something along the lines of:

route add default 0.0.0.0 gw 200.111.130.1 netmask 255.255.255.0 dev eth0

now thats off the top of my head after a long day of work. But network connectivity will not work without a default route, why it's not providing you one when you do a 'service network restart' is beyond me, but the above is worth a try.

-Scott

Scott, I've already tried something similar:

route add default gw 200.111.130.1

Is there a chance that this command has failed, and that the command you suggest:

route add default 0.0.0.0 gw 200.111.130.1 netmask 255.255.255.0 dev eth0

will work?

I suppose it's worth mentioning (but you've probably already done it) ...to turn off iptables and be sure your hosts.allow and hosts.deny are not getting in the way.
Your ifconfig shows no packets received or transmitted. That is a bad sign.

Both hosts.allow and hosts.deny are void, as this is a brand new fedora core 5 standard installation.

I've completely turned off iptables.
Nothing happens.

Scott:

Besides is really strange that knoppix installed so well in less than 3 minutes and the network is still not working, isn't it?

Alejandro

Uffffffff, finally I've consulted a linux guru that made what follows:

He installed windows 2003 server for 64bits on the machine, which is a AMD 64 bits on a mother Assus AV8MX.

Everything worked perfect. Then he tried different versions of the linux kernel and he atributes the problem to an incompatibility between the verision of the kernel I am trying to install (it's a fedora core 5 for x86_64)and the mother from assus.

Notably nobody reported this kind of incompatibility that is supposed to happen on the asignation of interruptions of the mother.

This beloved guru told me that he will suggest a couple of alternatives in order to get things up and running.

Thank you all for your answers. I will post the solution if I am able to find it.

Alejandro

Sir,

I got the same problem. Same mother board and trying to make network "on", on FC5 x-64 installation.


Alex

I finally changed the motherboard and the chip to intel and everything worked perfect. Also with the mother assus av8mx I wasn't able to use SATA disks, whereas no problem with the intel motherboard.

It's a compatibility problem, but unfortunately it took one month and a half and a good deal of money solve the problem.

Alejandro