F1!! Linux + XP crossover doesn't work.

[chutzpa]

hey, guys!
I installed Linux RH 7.3 Yesterday... didn't sleep the entire nite.
Eventually everything is fine but this stupid connection with my XP machine.
Everything seems to be 100% alright, by the book. I even went through NAG..

Anyway, eth0 is recongized, assigned 192.168.0.1; route table has the network interface (192.168.0.0), Windows sees the connection (a help frame pops up saying found a connection) - no problem there supposedly.
But both boxes can't ping each other.

I have no idea what it could be.
The card (Linux) should be alright since windows sees it when i plug the cord in.

PLZ, after that much torment, i need to get that bastard over with.

Thanks a lot!!!

With respect,
Eli.

[chutzpa]

thanx for reply.

Alright,
XP box == 192.168.0.3
Linux Box == 192.168.0.1, netmask 255.255.255.0, default gateway and broadcast.

Both cards are found.

I looked up ifconfig eth0, route.

in ifconfig everything is et up as described above.
route has lo (127.0.0.0) and eth0 (!92.168.0.0)


That's pretty much it..

Oh, and i tried to pig from both boxes.... didn't work.

Thanx again!

[chutzpa]

where did you reply go?
weird..

[Gaccm]

is there a hub or router inbetween? try a cross-over cable to be 100% it isn't the hardware. If you don't have a croos-over cable, look at the hub/switch/router when the comps ping each other. If BOTH lights flicker (the light for the xp comp and the light for the linux box), then your hub/switch/whatever is working fine.

[chutzpa]

I appreciate ur reply, but...

Nope...i have a direct connection between them -- no hubs, no switches.

The cable IS ok, since windows can detect when it is plugged or not.

I tried to monitor traffic with ethereal, but it gives a weird result which i can't digest:)

I'll post etehreal's result (for trying to ping the XP machine) in 2 secs.

Thanx a lot!

[Gaccm]

do you have any other computers on the network? or is it possible to get online with your linux box? If the NIC absolutely 100% works, I have no idea. At a LAN party i was recently at, 1/2 of us couldn't ping the other 1/2. Only 1 computer could see all, which was good enough for us since you only need 1 server.

[chutzpa]

heres the output by tcpdump when trying to ping XP (192.168.0.3):
------------------------------------------------------- CUT
22:00:33.200000 arp who-has 192.168.0.3 tell 192.168.0.1
--------------------------------------------------------------------------

192.168.0.3 -XP
192.168.0.1 -Linux (pinging rom Linux)

[chutzpa]

I only have the Linux and XP machines and i really need to have them work ... i'm migrating to Linux for networking functionality..
It's really important.

I can;t start setting up DHCP and DNS without the connection working.


Thanx 4 reply.

[chutzpa]

Yeah, i can get online through ppp and everything is ok there.
But that sucker seems to have everything ok in the settings too but isn't working...

Mannnnnnnnnnnnnnnn

[chutzpa]

btw, the card works 100% because it can successfully ping the broadcast address of the network through the card.

[teeitup]

Gaccm had the best advice, YOU NEED A CROSSOVER CABLE!!!!!

Since you are connecting them together directly you MUST use one.
A hub or switch takes care of this for you. If you don't use either the cable has to be wired to make:

box 1 box 2
receive <-> transmit
transmit <-> receive

with out a crossover you get this.

receive <-> receive
transmit <-> transmit

If you don't, you'll get confusing results just like your post says.

The card will see the cable, the link light will come on, but still no communication.

If you can ping localhost that means your TCP/IP protocol loaded properly. The ping never leaves the machine.

Good Luck,

[chutzpa]

thanx for reply.

But i AM using a crossover as it says in the titile of the post.

As far as i know 127.0.0.1 never goes through eth interfaces so it does not demonstrate anything.

The thing is that it actually CAN ing 192.168.0.255 and 192.168.0.0 through thr card so the traffic does come through the card.

I know it sounds impossible... everything is riple checked "by the book" :)

Thanx for you response!
I really appreciate it.

[chutzpa]

damn it!!
sorry for the typoz:)

Shoot i already set up DNS,Sendmail and DHCP locally the only thing left is that sucker:)

[Gaccm]

well, lets keep getting rid of obvious things like, do you have a firewall? have you tried anyother things becides pinging (nmap, connecting to a running server)?

Also, you say you followed it by the book, what page were you following to get this?

actually, have you messed around with the route command? that could have messed something up.

[DMR]

Originally posted by chutzpa
As far as i know 127.0.0.1 never goes through eth interfaces so it does not demonstrate anything.It demonstrates that your TCP/IP stack is functioning.

Originally posted by chutzpa
The thing is that it actually CAN ing 192.168.0.255 and 192.168.0.0 through thr card so the traffic does come through the card.Bad news, though: that indicates nothing about said traffic actually reaching another node on the network; pinging the network and broadcast addresses will work with no cable plugged into the NIC at all.

Just do a straight ping from each machine to the other and make sure both results are positive. From the linux box:[root@penguinbox~]# ping -c5 192.168.0.3
PING 192.168.0.3 (192.168.0.3) from 192.168.0.1 : 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=0 ttl=255 time=1.566 msec
64 bytes from 192.168.0.3: icmp_seq=1 ttl=255 time=143 usec
64 bytes from 192.168.0.3: icmp_seq=2 ttl=255 time=168 usec
64 bytes from 192.168.0.3: icmp_seq=3 ttl=255 time=166 usec
64 bytes from 192.168.0.3: icmp_seq=4 ttl=255 time=163 usec

--- 192.168.0.3 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.143/0.441/1.566/0.562 msPinging from the XP box should be the same. Is this the sort of ping result you get?

Also, you might want to post the actual output of the route command...