asked on

canot even ping between windowz and linux

hi i have set up my rtl8139(A) network cards on my linux(SuSE6.2)
i have set up the ip and netmasks like this
192.168.1.1 255.255.255.0 linux box irq:11
192.168.1.2 255.255.255.0 windowz box irq:11

i set the ip address up in windowz
i got to the networking section then i select the tcp/ip section for my network card and fill every thing in there

i fill in the networking info for my linux box in YAST

but when i try and ping to the windowz box from the linux box there is activity on the hub,on the back of the network card on the linux box and on the back of the windowz box
but it isnt responding
and
and the windowz box cannot oing the linux box

i honestly dont know what is going
please help

rwenzla

Can the windows box ping the linux box?
One or the other might have their IRQ set wrong
so they get no indication that there is an incoming
packet. The ethernet card sees the activity (lights flicker), but doesn't get the CPU's attention because the wrong IRQ line goes high. This is sometimes a problem with Plug and Play devices. Some config tool will hard code an IRQ in a config file, and somewhere along the line, the PnP will reconfigure.

Since you said there's a hub, I'm assuming 10baseT, so termination isn't an issue, on 10Base2 the "collision" light would give that away.

strikie

ASKER

Edited text of question.

deltree

Also, can you ping yourself on each system? If not, you may have bad IP stack on one/both side(s). Or a bad NIC.
If you can, you may have a bad cable or port on the hub.

strikie

ASKER

so i should chang the ips
and how do i change NIC

and the cables and hub aer fine ive run diognostic progies on both comps

drittich

Before you try any hardware solution, remove all clients, adapters, protocols, and services from your Windows network setup. Reboot your computer, and just reinstall the driver for the network adapter, and TCP/IP bound to the same adapter. No client, nothing else. Then retry the pings.

You didn't mention what version of Windows, but Win95 was notorious for the protocol stack getting messed up, where a simple removal and reinstall fixes things.

helver

on your linux box, what does the output of the route command show you?

strikie

ASKER

route shows this;
Destination gateway genmask
home * 255.255.255.0
loopback * 255.0.0.0
flags metric ref use iface
U 0 0 0 eth0
U 0 0 0 lo

helver

for your win95 box, make your linux box the default gateway.

for you linux box try running the following:

route add default eth0

unless you're going to be adding another interface (ppp, slip)...

gjlynx

From all of the comments I cannot tell if you can
ping your self from each of the machines.
Also what do you get when you run ifconfig on
the Linux box?

ASKER CERTIFIED SOLUTION

tiwari

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

strikie

ASKER

heres what i get for my ehthernet card when i do the ifconfig command

Link encap:Ethernet HWaddr00:00:B4:A4:84:66
inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNINGMULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100
Interrupt:11 Base address:0xc000

what does windows m/c ip mean
does it mean the ip address of my windowz box cause when i did
#route add -host <192.168.1.98> dev eth0
the reply was
bash: 192.168.1.98: No such file name or directory

stardrake

I think he meant like this:
#/sbin/route add -host 192.168.1.98 dev eth0

helver

Has this been resolved yet?