X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: Wich privileges required by ssh-host-config running user? Date: Wed, 18 Jan 2006 15:38:37 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <43CE5EA0.6090609@equate.dyndns.org> Message-ID: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Chris Taylor wrote: > You want to try with the domain administrator account, not the local > administrator. > If you're logging on as administrator, and log on to is set to the > domain, then you are already doing so and something most unusual is > occuring - suggestive of an admin removing administrator access to the > root filesystem, or to certain parts of it. Bingo. That's it. In particular, joining a domain locks down the perms of your C:\ root drive. If, for instance, a folder under that relies on the default perms being inherited, it's going to be in trouble. I think this is a problem any time you install cygwin as a local admin, then join a domain, then try and use it as a domain user, although I may not have the precise order of events right there. But I'm certain the key to this problem is in the perm changes that get applied when you join a domain. Simplest workaround would be to always join the machine to the domain first and install cygwin second. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/