Yeah, physically removing the card is what I meant. There is probably a much better to fix this, but seeing as you aren't using that card right now, why not try that?

The route add command was just to add a default route (shouldn't change local traffic)

Try changing /etc/sysconfig/network-scripts/ifcfg-eth1 to:
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=static
IPADDR=192.168.1.1
NETMASK=255.255.255.0
GATEWAY=192.168.1.2

Then restart networking:
service network restart

I assume you have just tried connecting to a service like ssh or telnet that you know is running as well as trying pings?

Redhat has always been a tempremental little madame to me when it comes to having more than one network card.

If none of the route stuff works I'd go with the previous reply, take out the card you don't need and start from scratch unless you want to get in there and start creating and deleting files manually. Has it even created an ifcfg-eth1 file for you? Check in /etc/sysconfig/network-scripts for it (think thats the right location).

Let's update my progress.
Okay. I have removed the SiS card so we can now focus on only 1 card. The setup also removed all eth0 configuration so eth1 became eth0.
eth0 is now the RealTek card - the one used for lan. I had to delete both cards from the network configuration tool and add the realtek one/manually configure it. I only have one ethernet card now - eth0!

After removing 1 card/rebooting/reconfiguring/rebooting I was still unable to ping nor from linux nor from XP. Next I changed the config file.

The configuration file for eth0 (formerly eth1) now looks like this:
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
USERCTL=no
PEERDNS=yes
TYPE=Ethernet
DEVICE=eth0
BOOTPROTO=static
NETMASK=255.255.255.0
ONBOOT=yes
IPADDR=192.168.1.1
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
GATEWAY=192.168.1.2

After editing it as root/rebooting I was still unable to ping. It can easily ping itself... "ping 192.168.1.1" but not my XP machine "ping 192.168.1.2"

I have only tried pinging. If pinging doesn't work I assume nothing else will.

EDIT: Oops. Wrong config :P

EDIT2: Hey! The light on the network card blinks once a while. We're making progress here

Unless you are blocking pings:
cat /proc/sys/net/ipv4/icmp_echo_ignore*

If this returns 2 '0's then you shouldn't be if it returns 1s then echo 0 into the 2 files. This still wouldn't explain why you can't ping xp though.

Hmmm I have pretty much the same problem! have been working on it for a day now, can't understand what's wrong! pleeeease help!

Just stick to this thread. Hopefully we'll find out what's wrong here.

It returns 2 zeros:
0
0

I have a question by the way. While I was searching through my network settings suddenly this dialog popped into my eyes. Do you think THIS has anything to do with the problem? Here's a shot:
http://invis.free.anonymizer.com/htt...e/network1.gif

The settings are not configured so I thought this might be causing the problem.

hehe just solved my problem, was just to simple =)

Both my cards was in the same ip subnet, eth0 192.168.0.1 and eth1 192.168.0.57, changed eth1 to 192.168.1.57 and my local net could ping me and vice versa.... Still have som e problem with ip masq though... (i think i have fucked up every network conf file in my comp....)

Hope this can be to some help, if we had the same problem it should work for you with only one network card.

Good luck

//Erik

Ok. Nice to see your problem solved.
*cries*

I would also like to know where the configuration file for the linux kernel IP routing table is (the one "route" uses).

EDIT:

Typing "cat /proc/interrupts" returns the following:

CPU0
0: 351108 XT-PIC timer
1: 625 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 2560 XT-PIC via82cxxx
8: 1 XT-PIC rtc
10: 0 XT-PIC usb-uhci, usb-uhci, eth0
12: 50403 XT-PIC PS/2 Mouse
14: 14511 XT-PIC ide0
15: 205781 XT-PIC ide1
NMI: 0
ERR: 0

Is everything here okay? No conflicts? I'm a bit concerned about the zero at interrupt #10 - the one for eth0

it seems i have a simliar problem.

i have one windows xp box and one redhat 9 box hooked up to a d-link router that is a gateway to my cable modem.

my xp box (192.168.0.100) can ping the router (192.168.0.1) and the linux box (192.168.0.101) fine, but my linux box can only ping the router, but NOT the xp box. it can access the internet (im currenly posting from the linux box).

i have 2 ethernet cards on my linux box (i was originally and still might use it as the gateway). eth0 is onboard, and eth1 is a d-link PCI nic. eth0 is connected to the router, and eth1 is connected to the mobo (and linux recognises it), but has no cables connected whatsoever.

cat /proc/sys/net/ipv4/icmp_echo_ignore* returns two "0"s.

ifconfig returns
eth0 Link encap:Ethernet HWaddr 00:0C:6E:50:AE:31
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1937 errors:0 dropped:0 overruns:0 frame:0
TX packets:684 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:693723 (677.4 Kb) TX bytes:102080 (99.6 Kb)
Interrupt:5 Base address:0x8800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4251 errors:0 dropped:0 overruns:0 frame:0
TX packets:4251 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:290105 (283.3 Kb) TX bytes:290105 (283.3 Kb)

cat /etc/sysconfig/network-scripts/ifcfg-eth0 returns
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
USERCTL=no
PEERDNS=no
TYPE=Ethernet
NETWORK=192.168.0.0
IPADDR=192.168.0.101
NETMASK=255.255.255.0
HWADDR=00:0c:6e:50:ae:31
GATEWAY=192.168.0.1
BROADCAST=192.168.0.255

oh, and i forgot to mention. i have an apache server running on the linux box on port 80. i have also set up a virtual server on my router to foreward 24.171.143.42:80 (my router's ip on the wan) to 191.168.0.101:80. i can access http://192.168.0.101:80 and have the proper page be displayed from my xp box, but not http://24.171.143.42:80. i dont know if that helps, but that is the main reason for me purchasing the server.


i am just starting to learn about networking as well as rh9, so im quite a novice at this.

Hmm, Origy -- I'm glad to see you're sticking with this, it canbe frustrating at times.

Let's see... I think we've determined that your drivers are working correctly for the Realtek card.

To doublecheck, by using the command "lsmod" (stands for list modules), does it return rtl8139 or 8139too ?

Those are the two drivers that work for the 8139 card, one I use here at home.

Hmm... Now your routing table should be set up correctly too.
The cables are all good, as you say, and you get a link-light on the back of the card and at the switch as well.
This means everything is communicating at the hardware level.

Use the command
This will list absolutely *everything* that the interface eth0 sees. Whether or not routing tables are set up correctly, etc -- now with that running, go and ping your computer from an XP box.
See if it reports anything.

Let's work from here

-Shade