delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/09/10/07:16:44

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
Message-ID: <2899.10.0.0.7.1094815161.squirrel@mail.equate.dyndns.org>
In-Reply-To: <20040910084618.GU17670@cygbert.vinschen.de>
References: <20040909202553 DOT 8B672E598 AT wildcard DOT curl DOT com> <4140C972 DOT 6030408 AT iwcenter DOT com> <20040909220929 DOT GA30475 AT cygbert DOT vinschen DOT de> <41416396 DOT 48B2E11E AT dessent DOT net> <20040910084618 DOT GU17670 AT cygbert DOT vinschen DOT de>
Date: Fri, 10 Sep 2004 12:19:21 +0100 (BST)
Subject: Re: rsync + xp sp2 failing
From: "Chris Taylor" <chris AT equate DOT dyndns DOT org>
To: cygwin AT cygwin DOT com
User-Agent: SquirrelMail/1.5.1 [CVS]
MIME-Version: 1.0
X-IsSubscribed: yes

On Fri, September 10, 2004 9:46 am, Corinna Vinschen said:
> On Sep 10 01:19, Brian Dessent wrote:
>
>> Corinna Vinschen wrote:
>>
>>
>>> All WSADuplicateSocket calls fail with 10045, "operation is not
>>> supported for the type of object referenced", even thought the above
>>> created socket handles are referenced.  That's weird.
>>>
>>> I'm still running XP SP1 and I can't reproduce this.  I'm wondering
>>> if that's a side effect of the new firewall in XP2.  Did you try with
>>> switching off the firewall entirely?
>>
>> FWIW this error happens frequently enough for Apache under windows that
>>  it's in their FAQ:
>> <http://httpd.apache.org/docs/misc/FAQ.html#WSADuplicateSocket>
>>
>>
>> ---- quote ----
>> Apache for Windows does not start. Error log contains this message:
>> "[crit] (10045) The attempted operation is not supported for the type of
>>  object referenced: Parent: WSADuplicateSocket failed for socket ###".
>> What does this mean?
>>
>
> Interesting.
>
>
>> And finally, although it's probably not relevant, the following passage
>>  from
>> <http://msdn.microsoft.com/security/productinfo/xpsp2/default.aspx?pull
>> =/library/en-us/dnwxp/html/securityinxpsp2.asp>
>> might help track down the problem:
>>
>> ---- quote ----
>> IPv4 Inbound Connections for Applications. An application that completes
>>  a listen operation on a TCP socket or successfully binds to a UDP
>> socket through Winsock is covered by this scenario. Examples of these
>> applications include audio and video in MSN or Windows Messenger, or
>> hosting a multiplayer game. For this scenario, ICF can automatically
>> open and close ports as needed by the application. When an application
>> that needs to listen on a port or ports is being installed by an
>> administrator, it will need to ask the user if he/she wants to allow
>> the application to open ports in the firewall. If the user consents to
>> this, then the application should use the INetFwV4AuthorizedApplication
>> API to
>> add itself to the AuthorizedApplications collection as enabled. If the
>> user does not consent, then the application should use the
>> INetFwV4AuthorizedApplication API to add itself to the
>> AuthorizedApplications collection as disabled.
>> ---- end quote ----
>>
>
> I *pray* it's not related.
>
>
>
> Corinna
>
>

Is it possible this is due to the changes in tcpip.sys and/or the tcp
stack? I myself am using a hacked one without these changes, so I could
test things to see if it is, if people can give me a specific set of
things to do ;-)
Unfortunately, half of the stuff in this thread went clean over my head,
so I could easily be barking up the wrong tree....

Chris

-- 
"And the Lord spake, saying, 'First shalt thou take out the Holy Pin. Then
shalt thou count to three, no more - no less. Three shall be the number
thou shalt count, and the number of the counting shall be three. Four
shalt thou not count, neither count thou two, excepting that thou then
proceed to three. Five is right out! Once the number three, being the
third number, be reached, then lobbest thou thy Holy Hand Grenade of
Antioch towards thy foe, who, being naughty in my sight, shall snuff it.'"



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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019