X-Spam-Check-By: sourceware.org Message-ID: <31b7d2790703151401o7872d738vb501ecadfac36be5@mail.gmail.com> Date: Thu, 15 Mar 2007 15:01:52 -0600 From: "DePriest, Jason R." To: cygwin AT cygwin DOT com Subject: Re: Accessing remote PC (ssh?) In-Reply-To: <45F9B2DF.1020703@bellsouth.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45F9B2DF DOT 1020703 AT bellsouth DOT net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 3/15/07, Charles D. Russell wrote: > * "Larry Hall wrote: > > > .ssh/known_hosts on dell03 contains explicit IP addresses for both > dell03 and sony06 that are no longer current. > > Move this file out of the way and try ssh again. > __________________________________ > > > Success! That's all it took. > > I suppose I'll have to repeat this every time DHCP changes the IP addresses. > > > What little I know about networking makes me fear blundering into a > morass if I depart much from the default installation scripts. Also, > my existing DHCP configuration works with Knoppix and other linux live > disks. So I think I'll stick with DHCP. > > -- If it's your DHCP, just make sure the lease expiration is long enough so that your systems won't lose their IP if they are shut-down for a period of time. Also, if a system ever picks up the IP of another system you have SSH'd in to, you will get an error about the keys not matching and you will not be able to connect. You will have to edit your known_hosts and take out the offender. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/