This is apparently a known, and intentional, issue with Winsock. Read Microsoft Knowledge Base Article - 173619 at: http://support.microsoft.com/default.aspx?scid=kb;EN-US;173619
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.