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-L'" <cygwin AT cygwin DOT com>
Subject:	RE: running the latest cygwin on a windows 2003 server
Date:	Wed, 21 Jan 2004 17:37:19 -0000
MIME-Version:	1.0
In-Reply-To:	<400EAE3B.5090301@etr-usa.com>
Message-ID:	<NUTMEGlb5fA2yiwwXkp0000017a@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	21 Jan 2004 17:37:19.0391 (UTC) FILETIME=[3807DAF0:01C3E045]

 

> -----Original Message-----
> From: cygwin-owner On Behalf Of Warren Young

> Stefan Zachow wrote:
> > 
> > "why is this all happening only to the Windows Server 2003 machine"?
> 
> Because Microsoft tightened down a lot of things in Win2K3 
> that previous Windows OSes allowed.
> 
> I upgraded a server from Win2K to Win2K3 a few weeks ago, and 
> already we've been bit by two of these paranoia changes.  I 
> don't yet have any experience that bears directly on your 
> problem; this is just a general observation.

You might both find some useful information in this article "Development
Impacts of Security Changes in Windows Server 2003":

http://msdn.microsoft.com/library/en-us/dncode/html/secure06122003.asp



    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 -