X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=GMG9iInjwiohMj54 sjO5hcFsoHBVEZzx+tGJxD8MR5U/bJl0yZzpVOGEz1oWPQs/XprteGOjulhodPlI z3E0uKMszvOB87f5s1HWaqrEzLvALtf3XAaY06jgTigriZSqJK9NWpeR8OhVsqmF xMXBuYgjOmEVaTP91jjzkTARy+c= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=default; bh=0QNtbFur5bH2kffHuRzTAT Z9GFQ=; b=jBhCbVPBUaxnOUtfUD4XTxrS9Rl9P6unxxTvazimMrgqWYTwmSWkWJ lFqJXYQu4odCD0rs4OFPVH97pCw0dxz8KlVpyiTsnrFUSeK7VcEh5WWdeCYiJxks 3uilc9pUuh/qjYalfuy1v0MhEybgWIRyQb/HYW4wfrZj7cn9yRDgA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RDNS_NONE autolearn=no version=3.3.1 Message-id: <52028508.7000102@cygwin.com> Date: Wed, 07 Aug 2013 13:34:00 -0400 From: "Larry Hall (Cygwin)" Reply-to: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: ssh logon failure References: <4FCF00EB DOT 2070600 AT gmail DOT com> <4FD07C1D DOT 5070909 AT gmail DOT com> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit On 8/7/2013 1:10 PM, Yuki Ishibashi wrote: > Marco and others: > > I also had the same problem, and ultimately was able to solve the problem by: > > - Completely removed any references to sshd and cyg_server in the > Windows user accounts and also in /etc/passwd > -Removed the "CYGWIN sshd" Service > (in a Run-as-Admin command line run 'sc delete sshd' ) > - Ran the cygwin terminal As-Admin and the /bin/ssh-host-config script, > re-creating the deleted accounts and services by exactly following this guide: > ( under 'Configuring OpenSSH in Cygwin')L > http://www.howtogeek.com > /howto/41560/how-to-get-ssh-command-line-access-to-windows-7-using-cygwin/ For the benefit of those that might find this set of instructions in a web search, the above link is not associated with nor supported by this list. Follow these instructions at your own risk and only if you know the consequences of doing so. This list recommends that you use Cygwin resources to help set up OpenSSH and other packages. Cygwin-specific documentation is available under the /usr/share/doc/Cygwin directory. > After that (and running 'net start sshd'), ssh services were restored. > If you're still having this problem > (and for anyone who had to madly google this problem) > I hope this helps. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple