Red Hat Linux server only connects to local network
 

I'm currently trying to setup the eth0 and eth1 of a server running Red Hat Enterprise Linux WS release 4. The following is the configuration of the two nics:

etho:

DEVICE=etho
TYPE=Ethernet
ONBOOT=Yes
BOOTPROTO=static
IPADDR=172.16.4.178
NETMASK=255.255.255.192
HWADDR=xx:xx:xx:xx:xx:
GATEWAY=172.16.4.129


eth1:
DEVICE=eth1
TYPE=Ethernet
ONBOOT=Yes
BOOTPROTO=static
IPADDR=192.168.3.4
NETMASK=255.255.255.0
HWADDR=xx:xx:xx:xx:xx:


and the /etc/sysconfig/network file:

NETWORKING= yes
HOSTNAME= XYZ


I can ping other machines in the local network, like 172.16.4.175, 177, 176. But
I cant even ping the gateway which is 172.16.4.129

I have 3 other machines in the local network that have pretty much the same network configuration, and
I have not problem with them.

this is the output of the "ip route show":

172.16.4.128/24 dev eth0 proto kernel scope link src 172.16.4.178
192.168.3.0/16 dev eth1 proto kernel scope link 192.168.3.4
169.254.0.0/16 dev eth1 scope link
default via 172.16.4.129 dev eth0


Any ideas onhow i can solve this issue,

Thanks

Avi

The version of RH you are using was released like 10 years ago and hit EOL a few years back. You will want to upgrade to something that is supported.

That being said,..

Can you ping your localhost?

Can you ping your eth0 address?

What does ifconfig look like?

Is the link up? Is the card good?

[root@drjves_New_Hope_04 bin]# ifconfig
eth0 Link encap:Ethernet HWaddr A4:BA:DB:E0:56:8E
inet addr:172.16.4.178 Bcast:172.16.4.191 Mask:255.255.255.192
inet6 addr: fe80::a6ba:dbff:fee0:568e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2648863 errors:0 dropped:0 overruns:0 frame:0
TX packets:43705 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:169714092 (161.8 MiB) TX bytes:2939880 (2.8 MiB)
Interrupt:16

eth1 Link encap:Ethernet HWaddr A4:BA:DB:E0:56:8F
inet addr:192.168.3.4 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::a6ba:dbff:fee0:568f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7195 errors:0 dropped:0 overruns:0 frame:0
TX packets:31218 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:638077 (623.1 KiB) TX bytes:1998440 (1.9 MiB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3434351 errors:0 dropped:0 overruns:0 frame:0
TX packets:3434351 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:218093722 (207.9 MiB) TX bytes:218093722 (207.9 MiB)

I cant ping the host. I am able to ping eth0 within the local network attach to the same switch but i can not go beyond that point. From the main host I cant pin etho.

The link is up and I assume the nic card too, because it responds to ping within the local network.

The output of `ip route show` , uh, shows "172.16.4.128/24 ...." the mask should be /26. That may be defeating the arp requests as the broadcast address would be incorrect, assuming that isn't a typo.

The gateway, if it's also a firewall, may not allow pings. I'd check that before I spend a lot of time trying to figure out why replies aren't being sent back. Can other hosts ping the gateway?

It looks like both NICs are working fine; lots of data send and received with no errors.

Is the DEVICE= line really etho (that's eth-OH and should be eth-zero)?

also RHEL4 is unsupported by redhat

rhel 4.9 is on EXTRA extended support for 1 more month
as in you had to pay extra and only 4.9 was extended

rhel4 has NO support for new hardware and no ipv6 support .

please upgrade ASAP
RHEL6.5 is the current and RHEL 7.0 will be released SOON

Thank you John VV and MikeDeltaBrown for your help.
That is fixed. I swapped the ethernet cables from the back of the server(etho and eth1) and suddenly the connection to the rest of the network was reestablished.
Each cable was connected to the wrong switch.

Thanks again

Now, right after the connectivity issue was resolved. The following broadcast message started to show up in all the machines of the local network

[root@drjves_New_Hope_04 bin]#
Broadcast message from root (Wed Jun 4 23:29:09 2014):

KILLING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

Broadcast message from root (Wed Jun 4 23:29:09 2014):

KILLING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

Broadcast message from root (Wed Jun 4 23:29:10 2014):

STARTING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

Broadcast message from root (Wed Jun 4 23:29:10 2014):

STARTING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

[root@drjves_New_Hope_04 bin]#
Broadcast message from root (Wed Jun 4 23:34:50 2014):

KILLING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

Broadcast message from root (Wed Jun 4 23:34:50 2014):

KILLING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

Broadcast message from root (Wed Jun 4 23:34:51 2014):

STARTING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

Broadcast message from root (Wed Jun 4 23:34:51 2014):

STARTING das_Plaza_Host_Comm on drjves_New_Hope_04 via restart

I do not know why or how to stop it,

Thanks