Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 6 Jun 2005 21:49:58 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin.bat fails with "WFMO failed waiting for cygthread 'WnetGetResourceInformation'
Message-ID: <20050606194958.GA23172@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <15119943 DOT 1118075991634 DOT JavaMail DOT tjhart AT mac DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <15119943.1118075991634.JavaMail.tjhart@mac.com>
User-Agent: Mutt/1.4.2i

On Jun  6 11:39, Tim Hart wrote:
> All,
> 
> My XP machine is currently unable to connect to my Windows domain before logging in. Windows uses cached information to accept my domain login. I then VPN to my domain, and life is good.
> 
> If my VPN connection is established, then Cygwin works just fine. If, however, I am not connected to my VPN, then I see the message:
> 
> C:\cygwin\bin\bash.exe (1672): *** WFMO failed waiting for cygthread 'WnetGetResourceInformation'
> 
> This behavior is different than on previous versions of Cygwin - I could launch bash(cygwin.bat) just fine whether or not I was connected to the domain.
> 
> If this change is intentional, then I would like to discuss the matter. Are you really beefing up security by not allowing me to run bash & the cygwin subsystem? Even though Windows accepts the login and will let me run anything else that doesn't require Domain resources?

This has nothing to do with security but with accessing shares on the
network.  Apparently you're accessing shares which are only available
when the VPN is up and this *somehow* results in some internal problem.

Unfortunately you're only giving very basic information.  Please have a
look into http://cygwin.com/problems.html and follow the guidelines for
reporting problems.  Especially add some clue how shares come into play.
Any share you're accessing always in, say, your .bashrc?  Yes?  No?  How?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/