re: the Windows 2000 0.0.0.0 IP address problem Bill,
Both solutions work. Applying win32sock_is_known.patch corrects the problem for win2000. The Win32DisableAcceptEx directive also works to correct the problem (without the patch). -tom- William A. Rowe, Jr. wrote:
It's actually apr_os_sock_make() and although it set unknown=1 where there was no remote addr, it assumed unknown from alloc_socket() was 0. Try the attached patch please? Bill
William A. Rowe, Jr. wrote: > Tom, speculating here without a 2000 box close - would you try to > DisableWin32AcceptEx please? Perhaps the flaw actually resides in how > AcceptEx and GetAcceptExSockaddrs, and how they interact with the socket? > > Bill >
