Can't connect to apache 1

[MikeThornton]

Hi

I am new to using apache and I have a problem.

I have installed apache 2 on an xp home pc and the setup completed without problem and the apache service is running.

The only problem is that when I try to connect to localhost or even 127.0.0.1 the browser can't retrieve any web pages.

I can ping 127.0.0.1 so i am guessing it's a problem with my apache installation but I have tried re-installing with no luck. Any ideas?

Cheers

Mike

 

[feherke]

Hi

I do not know any port scan program for Windows, but I would try with [tt]telnet[/tt] :

telnet localhost 80

This way you will know if anything is listening on the default HTTP port.

Could you tell us abit more about that "the browser can't retrieve any web pages" ? If no page, then what is displayed ?

Feherke.

http://rootshell.be/~feherke/

 

[MikeThornton]

I tried Telnet and that didn't return anything at all. The browser simply sits for a lengthy period of time before returning the standard web page is unavailable error page.

If you want a list of ports, here you go :

Active Connections

Proto Local Address Foreign Address State
TCP mike-laptop:http mike-laptop:0 LISTENING
TCP mike-laptop:epmap mike-laptop:0 LISTENING
TCP mike-laptop:microsoft-ds mike-laptop:0 LISTENING
TCP mike-laptop:http localhost:1257 CLOSE_WAIT
TCP mike-laptop:http localhost:1926 CLOSE_WAIT
TCP mike-laptop:http localhost:1960 ESTABLISHED
TCP mike-laptop:1026 mike-laptop:0 LISTENING
TCP mike-laptop:1960 localhost:http ESTABLISHED
TCP mike-laptop:10110 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:1494 mike-laptop:0 LISTENING
TCP mike-laptop:netbios-ssn mike-laptop:0 LISTENING
TCP mike-laptop:1050 baym-cs123.msgr.hotmail.com:1863 ESTABLISHED
TCP mike-laptop:1111 193.118.251.57:https ESTABLISHED
TCP mike-laptop:1961 193.118.251.57:https ESTABLISHED
UDP mike-laptop:microsoft-ds *:*
UDP mike-laptop:isakmp *:*
UDP mike-laptop:1044 *:*
UDP mike-laptop:1045 *:*
UDP mike-laptop:1059 *:*
UDP mike-laptop:4500 *:*
UDP mike-laptop:ntp *:*
UDP mike-laptop:1030 *:*
UDP mike-laptop:1043 *:*
UDP mike-laptop:1051 *:*
UDP mike-laptop:1900 *:*
UDP mike-laptop:discard *:*
UDP mike-laptop:ntp *:*
UDP mike-laptop:netbios-ns *:*
UDP mike-laptop:netbios-dgm *:*
UDP mike-laptop:1900 *:*
UDP mike-laptop:15560 *:*

 

[feherke]

Hi

Ok, [tt]telnet[/tt] was just to check for connection. If no error, seems this is ok. ( To get the web page in [tt]telnet[/tt] you have to type in a request, just as the browser would do. )

Next step. Is anything written in the Apache access log and/or error log after such attempt ?

Feherke.

http://rootshell.be/~feherke/

 

[MikeThornton]

Thousands of :

[Thu Oct 27 17:24:53 2005] [error] (OS 10038)An operation was attempted on something that is not a socket. : Child 876: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive.

I looked in httpd.conf but couldn't find any reference to this directive. I do have a firewill(XP's own) but it still doesn't work when this is disabled.

Cheers

Mike

 

[feherke]

Hi

Pity. The firewall would be my next question. So I have no more idea. About that directive read it's module's doc :

http://httpd.apache.org/docs/2.0/mod/mpm_winnt.html

Feherke.

http://rootshell.be/~feherke/

 

[bonifale]

Hi,

Try using ShieldsUp to see if the port you are using, 80 usually, is open or being blocked by your firlewall

https://www.grc.com/x/ne.dll?bh0bkyd2

 

[MikeThornton]

I Have to admit my ignorance here. The Win32DisableAcceptEx directive worked eventually. The only reason it didn't work at first is that I had placed it in the wrong httpd conf file as I had re-installed apache in a slightly different folder. I'm sure there's a lesson in that somewhere!

Cheers for the help guys.

Mike