On Thu, May 6, 2010 at 10:08 AM, wrote: > > I had rsync working fine between two computers on my local network, but > then it just quit working even though I had made no changes in either > computer. > > This is the error message I saw: > ssh: connect to host 192.168.0.73 port 22: No route to host > This means that there is no route to the host > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > This means that the connection unexpectedly closed. > rsync error: error in rsync protocol data stream (code 12) at io.c(601) > [sender=3.0.7] > ssh: connect to host 192.168.0.73 port 22: No route to host > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: unexplained error (code 255) at io.c(601) [sender=3.0.7] > > Upon investigating, I found that the ip number on the "73" computer was > changed from 192.168.0.73 to 192.168.1.106. I tried changing the > destination address to "1.106" on the sending computer and that also did > not work. So I rebooted the destination computer and found that the ip > number was restored to "0.73" again. > > What would cause the ip number to have changed like that and how can I > prevent that from occurring again in the future? > > The only ways to change ip addressing on an interface are: 1) DHCP configuration 2) Human intervention > > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > -- Office: (480)307-8707 AT&T: (503)754-4452 Systems Engineer www.ivedaxpress.com