On Friday 22 January 2010 12:24:43 Rodolfo Medina wrote: > Johannes Wiedersich <[email protected]> writes: > > Check and possibly post the output of "/sbin/ifconfig" > > > > "ssh -v [email protected]" might also help to diagnose your problem. > > Still needing your help: > The `ping' command from first machine: > > $ ping 192.168.0.2 > PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. > > --- 192.168.0.2 ping statistics --- > 5 packets transmitted, 0 received, 100% packet loss, time 4000ms > > , and analogously from second.
Most likely, the two computers still can't send packets to each other. Make
sure you are using the correct type of cable. You'll need a crossover cable
if neither side is a 1Gbit card. You should probably use a crossover cable
anyway.
Make sure the cable runs to/from the physical port that is eth0 on both side.
There could be some routing issues, too. But that would only be if one of
your other ports was using a 192.168.0.x address as well, or if you've got
some routing customizations.
Until you can get the pings to work ("X packets transmitted, X received, 0%
packet loss") any other sort of network protocol is not going to work either.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
[email protected] ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
signature.asc
Description: This is a digitally signed message part.
