Synchronize two computers
in [Debian]
|
Prev: Problem with Lenny
Next: Unable to start tightvncserver
From: Johannes Wiedersich on 22 Jan 2010 04:40 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. Check and possibly post the output of "/sbin/ifconfig" "ssh -v user(a)192.168.0.2" might also help to diagnose your problem. - -- Johannes Three nations have not officially adopted the International System of Units as their primary or sole system of measurement: Burma, Liberia, and the United States. http://en.wikipedia.org/wiki/Si_units -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktZcL4ACgkQC1NzPRl9qEWtPQCdErh05t400nXwG4zAiElA30Fb bqIAn10/iG0DbjgF2VSBjp0kbzDU6nUA =PMyJ -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Alexey Salmin on 22 Jan 2010 04:50 On Fri, Jan 22, 2010 at 3:23 PM, Rodolfo Medina <rodolfo.medina(a)gmail.com> wrote: > On 10-01-21 14:17:37, Rodolfo Medina wrote: > >>> $ rsync -vru --delete ssh://192.168.0.2/home/rodolfo/test1 >>> /home/rodolfo/ >>> >>> but got error: >>> >>> ssh: ssh: Temporary failure in name resolution >>> rsync: connection unexpectedly closed (0 bytes received so far) >>> [receiver] >>> rsync error: unexplained error (code 255) at io.c(453) >>> [receiver=2.6.9] >>> >>> What did I miss?? > > > Tony Nelson <tonynelson(a)georgeanelson.com> writes: > >> Proper syntax from the rsync man page. You're telling rsync to connect >> to a host named "ssh". Try "192.168.0.2:/home/rodolfo/test1" instead. > > > 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. > > Further help very much appreciated. > > Rodolfo > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian..org > > 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 Alexey -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Rodolfo Medina on 22 Jan 2010 05:10 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 <johannes(a)physik.blm.tu-muenchen.de> writes: > Check and possibly post the output of "/sbin/ifconfig" > > "ssh -v user(a)192.168.0.2" might also help to diagnose your problem. Alexey Salmin <alexey.salmin(a)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 rodolfo(a)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-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Celejar on 27 Jan 2010 09:30
On Thu, 21 Jan 2010 17:20:49 +0530 Kousik Maiti <kousikster(a)gmail.com> wrote: > You need cross connected cable to connect 2 pc via lan card . > http://en.wikipedia.org/wiki/Ethernet_crossover_cable IIUC, many (most?) ethernet cards today support auto-crossover, which means that you can use a crossover or a patch cable, and the cards will figure it out. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org |