Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: running the latest cygwin on a windows 2003 server
Date:	Wed, 21 Jan 2004 17:45:46 -0000
MIME-Version:	1.0
In-Reply-To:	<400EA309.1050204@zib.de>
Message-ID:	<NUTMEGtZLz1UyZ0DiGy0000017b@NUTMEG.CAM.ARTIMI.COM>
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/

- Raw text -