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
Message-ID: <40984BF2.679F6610@hot.pl>
Date: Wed, 05 May 2004 04:05:38 +0200
From: Jacek Trzmiel <sc0rp AT hot DOT pl>
MIME-Version: 1.0
To: "'Cygwin List'" <cygwin AT cygwin DOT com>
Subject: Re: shutdown( socket, SHUT_WR ) - unexpected behaviour - RESOLVED
References: <NUTMEG3Mpw6yL2m9lHi00000164 AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <409769B5 DOT 6050609 AT earthlink DOT net>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes


> Possible, but I suspect it's a problem on Jacek's machine.
> 
> Jacek: Win2K SP2 is pretty ancient. Is it possible to try this on a
> later SP? (SP4 is the latest, and there have been numerous hotfixes
> since it was released.)

I've installed SP4 (had most of hotfixes already) but it didn't fix
problem.

However I found source of bug.  Norton Internet Security was messing
with sockets.  Removing NIS related entries in
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\ and rebooting did
solve problem.  So, bye bye NIS, will have to tighten ifpw instead.

Thanks all for help.

Best regards,
Jacek.

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