httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: [users@httpd] Win32DisableAcceptEx
Date Thu, 01 Sep 2005 16:22:36 GMT
Grønn Demon wrote:
> Hello,
> 
> I have both OpenSSH (using the Cygwin port from sshwindows.sf.net) and 
> Apache 2.0.52 installed on my Windows XP SP2 system and don't use them 
> very frequently (I guess a new Apache version's already been released).

That's ok - .54 hasn't changed much in this respect below...

> Anyway, after some time I wanted to login to my box using SSH again, but 
> after login I got "connection reset by peer."
> Telneting to port 22 gave me "OpenSSH <version>" - and as soon as I had 
> entered something, the same thing: "connection reset by peer"

Yup - something on your network stack is borked...

> "What does this have to do with Apache?", you may ask.
> Haven given up on OpenSSH (which didn't even give me any debug info) I 
> decided to give Apache a try. The service started ok and netstat showed 
> that the server was listening on port 81.
> However, I couldn't establish a connection, not even after disabling 
> Microsoft's "firewall".
> 
> Error.log said:
> "Encountered too many errors accepting client connections. Possible 
> causes: dynamic address renewal, or incompatible VPN or firewall 
> software. Try using the Win32DisableAcceptEx directive."

Sure sounds like the network stack is borked...

> I used that direction and it worked - but I have mixed feelings about 
> this as I've never had any problems with Apache in the past.
> AFAIK I haven't installed any software that could affect this in the 
> past (I've been using the same virus scanner for ages).

Many many AV programs, firewalls, and other network-stack based spam
filters simply are borked.  Apache (and apparently OpenSSH) uses some
very sophisticated API's - and we had to add Win32DisableAcceptEx, and
recommend setting Sendfile Off, to get around all the providers which
simply didn't implement the entire WinSock2 API (correctly).  Even MS's
own

> Could this be due to some Windows update? Or has my PC been infected by 
> some worm?

Windows update often turns back on features you disabled/uninstalled if
it believes it's "Protecting" your computer.  Auto-updates of your AV
software might even break it.

And although you don't mention it, XP SP2 borked the localhost provider
AGAIN.  FYI - only 127.0.0.1 on XP SP2 works, although on every modern
OS you can use any 127.n.n.n address to perform a local loopback.  MS
apparently has a 'hotfix' - typical runaround with customer service if
you need to apply it.  I don't have the incident/kb # offhand.

Look in your protocols and adapters in the network control panel and
remove the 'extra' junk.  Then look at your AV software with suspicion
and try uninstalling (or crippling the 'network' protection).  One
example is the QoS (Quality of Service) driver which might be
interfering.

There's nothing wrong with Win32DisableAcceptEx on a dev/experimental
server - it's only suboptimal and not a great thing for a production
server.

Bill

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message