Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Dave Korn" To: Subject: RE: running the latest cygwin on a windows 2003 server Date: Wed, 21 Jan 2004 17:45:46 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <400EA309.1050204@zib.de> Message-ID: X-OriginalArrivalTime: 21 Jan 2004 17:45:46.0428 (UTC) FILETIME=[663F8FC0:01C3E046] > -----Original Message----- > From: cygwin-owner On Behalf Of Stefan Zachow > another question to this topic came into my mind: > > "why is this all happening only to the Windows Server 2003 machine"? Ah, but then you go and point out that... > Although the SAMBA problem appears on all machines. And you're using a domain, right? Is this related to the "Pre-Windows 2000 Compatible Access group" thingy? If you didn't configure that when you promoted your domain controller, it might well have restricted the access needed and that might be what's messing up the Samba server? I'm not too hot on this topic, but if you wanted to find out more there's loads of hits when you search on that phrase.... http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=pre-windows+2000+ compatible+access+group 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/