Rodolfo Medina wrote:
>> It doesn't work either. I think that the two pcs don't see each other: also
>> the command `ssh 192.168.0.2' produces nothing.
Johannes Wiedersich <johan...@physik.blm.tu-muenchen.de> writes:
> Check and possibly post the output of "/sbin/ifconfig"
>
> "ssh -v u...@192.168.0.2" might also help to diagnose your problem.
Alexey Salmin <alexey.sal...@gmail.com> writes:
> 1. Use /sbin/ifconfig to check if interfaces were configured properly
> I think you've missed "auto eth0" in both /etc/interfaces files. That
> means that ifaces will be up only by demand like that:
> $ sudo ifup eth0
> 2. When interfaces are up - use ping to check if machines sees each other
> 3. If ping is ok - use ssh to check if ssh connection works
# /sbin/ifconfig
ppp0 Link encap:Point-to-Point Protocol
inet addr:151.83.161.25 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:552 errors:16 dropped:0 overruns:0 frame:0
TX packets:552 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:467484 (456.5 KiB) TX bytes:89543 (87.4 KiB)
# ssh -v rodo...@192.168.0.2
OpenSSH_4.3p2 Debian-9, OpenSSL 0.9.8c 05 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.0.2 [192.168.0.2] port 22.
debug1: connect to address 192.168.0.2 port 22: Connection timed out
ssh: connect to host 192.168.0.2 port 22: Connection timed out
# ifup eth0
# 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 ---
135 packets transmitted, 0 received, 100% packet loss, time 134033ms
I can't read trough all that!
Rodolfo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
