Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-11 Thread William A. Rowe Jr.
On 7/7/2011 3:39 AM, Gregg L. Smith wrote: I have an error log full of these; [Thu Jul 07 00:15:58.010625 2011] [mpm_winnt:warn] [pid 2840:tid 1572] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. Greg... were you using

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-11 Thread Gregg L. Smith
Bill, I was using nothing, so by docs, the default is/was data. XP SP3, IPv6 Proto loaded Yes, APR_HAVE_IPV6 ==1 NVIDIA nForce 10/100/1000 v. 67.8.9.0 8/1/2008 This box originally came with Symantic, and I would assume it was able to sniff, but that was removed and it is just MSSE now,

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-10 Thread William A. Rowe Jr.
On 9/29/2011 7:30 PM, Jeff Trawick wrote: This is well past the point where one needs to know the Listen configuration, exact problem symptom, etc. ;) Either way it seems that there were some oddities around the presence/absence of IPV6_V6ONLY. In its absence APR should have been returning

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-10 Thread William A. Rowe Jr.
On 9/29/2011 2:41 PM, Eric Covener wrote: I took a look at this in the AM, and it looks like the acceptfilter none path is relying on data set only by AcceptEX (context-buffer) to fill in context-sa_server (child.c:590). In 2.2 the context-buffer is seeded by the 9x specific code. Seems

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-10 Thread Eric Covener
Precisely.  As we have context-buff allocated for all AcceptFilter schemes, I added the appropriate queries into that buffer in r1181140, and the world seems at peace again for just this short moment. Trying to fully resolve the 2.3 accptex thread -- Should I add a note about

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-10 Thread Steffen
Note: With 2.2.x not a single issue reported here with Win32DisableAcceptEx, with ipv6 and/or ip4. Idea to revert 2.3 back to the old behaviour ? On Monday 10/10/2011 at 21:23, Eric Covener wrote: Precisely. As we have context-buff allocated for all AcceptFilter schemes, I added the

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-10 Thread William A. Rowe Jr.
On 10/10/2011 2:34 PM, Steffen wrote: Note: With 2.2.x not a single issue reported here with Win32DisableAcceptEx, with ipv6 and/or ip4. Idea to revert 2.3 back to the old behaviour ? Nope, absolutely not. The old behavior had way too much distinct code between the 9x and nt code

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-10 Thread William A. Rowe Jr.
On 10/10/2011 2:22 PM, Eric Covener wrote: Precisely. As we have context-buff allocated for all AcceptFilter schemes, I added the appropriate queries into that buffer in r1181140, and the world seems at peace again for just this short moment. Trying to fully resolve the 2.3 accptex thread

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-10-10 Thread Stefan Fritsch
On Monday 10 October 2011, William A. Rowe Jr. wrote: On 10/10/2011 2:22 PM, Eric Covener wrote: Trying to fully resolve the 2.3 accptex thread -- Should I add a note about Win32DisableAcceptEx to mpm_winnt doc? Or even add it back in as a directive to point to AcceptFilter? Add at least

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-30 Thread William A. Rowe Jr.
On 9/29/2011 7:30 PM, Jeff Trawick wrote: This is well past the point where one needs to know the Listen configuration, exact problem symptom, etc. ;) Either way it seems that there were some oddities around the presence/absence of IPV6_V6ONLY. In its absence APR should have been returning

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-29 Thread William A. Rowe Jr.
On 7/7/2011 3:39 AM, Gregg L. Smith wrote: I have an error log full of these; [Thu Jul 07 00:15:58.010625 2011] [mpm_winnt:warn] [pid 2840:tid 1572] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. This might be

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-29 Thread Jeff Trawick
On Thu, Sep 29, 2011 at 2:58 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 7/7/2011 3:39 AM, Gregg L. Smith wrote: I have an error log full of these; [Thu Jul 07 00:15:58.010625 2011] [mpm_winnt:warn] [pid 2840:tid 1572] (OS 64)The specified network name is no longer available.  :

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-29 Thread Eric Covener
On Thu, Sep 29, 2011 at 2:58 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 7/7/2011 3:39 AM, Gregg L. Smith wrote: I have an error log full of these; [Thu Jul 07 00:15:58.010625 2011] [mpm_winnt:warn] [pid 2840:tid 1572] (OS 64)The specified network name is no longer available.  :

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-29 Thread William A. Rowe Jr.
On 9/29/2011 2:22 PM, Jeff Trawick wrote: On Thu, Sep 29, 2011 at 2:58 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 7/7/2011 3:39 AM, Gregg L. Smith wrote: I have an error log full of these; [Thu Jul 07 00:15:58.010625 2011] [mpm_winnt:warn] [pid 2840:tid 1572] (OS 64)The

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-29 Thread Jeff Trawick
On Thu, Sep 29, 2011 at 5:00 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 9/29/2011 2:22 PM, Jeff Trawick wrote: On Thu, Sep 29, 2011 at 2:58 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 7/7/2011 3:39 AM, Gregg L. Smith wrote: I have an error log full of these; [Thu Jul 07

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-29 Thread Jeff Trawick
On Thu, Sep 29, 2011 at 8:02 PM, Jeff Trawick traw...@gmail.com wrote: On Thu, Sep 29, 2011 at 5:00 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 9/29/2011 2:22 PM, Jeff Trawick wrote: On Thu, Sep 29, 2011 at 2:58 PM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 7/7/2011 3:39

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-09-29 Thread Gregg L. Smith
Bill, I think it's been realized that the APR/IPv6 has no bearing on this but I can confirm that 2.3.15-dev at r1177210 with apr 1.4.2 and ipv6 set to 0 does the exact same thing. Cheers, Gregg On 9/29/2011 11:58 AM, William A. Rowe Jr. wrote: On 7/7/2011 3:39 AM, Gregg L. Smith wrote: I

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-07-07 Thread Gregg L. Smith
Hi, I have an error log full of these; [Thu Jul 07 00:15:58.010625 2011] [mpm_winnt:warn] [pid 2840:tid 1572] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed. Thanks to Steffen's bringing this up, I now know how I should be fixing

Windows 2.3.13 :: Win32DisableAcceptEx

2011-07-04 Thread Steffen
The widely used Win32DisableAcceptEx is not anymore in 2.3. Can someone confirm that this has the same effect: AcceptFilter http none AcceptFilter https none Maybe an idea to update the upgrading docu on this subject ? Steffen

Re: Windows 2.3.13 :: Win32DisableAcceptEx

2011-07-04 Thread William A. Rowe Jr.
On 7/4/2011 9:46 AM, Steffen wrote: The widely used Win32DisableAcceptEx is not anymore in 2.3. Can someone confirm that this has the same effect: AcceptFilter http none AcceptFilter https none Maybe an idea to update the upgrading docu on this subject ?