Apache Web Server won't start - no listening sockets available error - 500 points!!!

I posted a question earlier, http://www.experts-exchange.com/Web/Web_Servers/Apache/Q_21843803.html, that relates to this problem.  Now I can find out why the Apache Web Server service is not starting but I don't know how to resolve the problem.  The error I'm getting is:

(OS 10048) Only one usage of each socket address (protocol/network/address/port) is normally permitted.  :make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down, unable to open logs

In summary, I have a Windows machine running Windows XP Pro SP2 that has 2 Web Servers installed on it.  The first one is Apache which I did not install and was assigned to ip address, xxx.xxx.xxx.74.  For another project that my client has going, the WebCrossing Web Server was installed and assigned to ip address, xxx.xxx.xxx.78.  If I type in the ip address for the WebCrossing Web Server, I get the correct website.  If I type in the ip address for the Apache Server I get the Page is Under Construction Message which appears to be in the default c:\inetpub\wwwroot directory which leads me to believe that MS IIS is started.  However, when I issue the iisrestart /stop command and go to the ip address for the Apache Server I still get the Page is Under Construction Message.

I'm very confused as to what is going on and would like to get the Apache Web Server and WebCrossing Web Server running on the same box.  Any help would be greatly appreciated!
dyaroshAsked:
Who is Participating?
 
NopiusCommented:
Your main mistake: Apache is NOT an IIS.
So this command: iisrestart /stop DOESN'T stop your Apache...

"(OS 10048) Only one usage of each socket address (protocol/network/address/port) is normally permitted.  :make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down, unable to open logs|

This error is shown because you are trying to bind apache to already captured 80 port.

As sleep_furiously said, check your apache config first and change line "Listen 80" or 'Listen *:80' to 'Listen xxx.xxx.xxx.74:80'. Otherwise your Apache tries to bind to ALL IP addresses 80 port, and attempt is failed because webxserv.exe is already there.
0
 
sleep_furiouslyCommented:
Shouldn't "iisrestart /stop" be "iisreset /stop"?  I'll assume that's just a typo.

What does "iisreset /status" show?

You can use a free tool like TCPView to see what processes are listening on port 80 for the various interfaces.
http://www.sysinternals.com/Utilities/TcpView.html  (It may be easier to sort out if you turn off name resolution under Options.  You do want to show unconnected endpoints, otherwise you will only see the listeners when they are doing something.)

You can go into IIS Manager and set IIS Web Site(s) to use a port number other than 80.

Check the conf file for the Apache server (and the WebCrossing server, assuming it is some sort of Apache).  You don't want to have "Listen 80", but something that binds to a specific IP, like "Listen xxx.xxx.xxx.74:80"
0
 
rama_krishna580Commented:
Hi,

Take a look at  http://www.apacheworld.org/ty24/, in the secure server chapter for detailed instructions on how to get Apache 2 works.
https://savannah.gnu.org/maintenance/CurrentIssues

R.K
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
dyaroshAuthor Commented:
iisreset /status shows:

Status for World Wide Web Publishing (W3SVC): running
Status for Simple Mail Transfer Protocol (SMTP) (SMTPSVC): running

TCPView shows the following:  (I'm only listing processes that reference the 2 ip addresses that I'm using or :80 port)

svchost.exe:1088 UDP xxx.xxx.xxx.74:123 *.*
svchost.exe:1088 UDP xxx.xxx.xxx.78.123 *.*
svchost.exe:1248 UDP xxx.xxx.xxx.78:1900 *.*
svchost.exe:932 TCP xxx.xxx.xxx.74:3389 xx.xxx.xxx.240:1042 Established
System4 TCP xxx.xxx.xxx.74:139 0.0.0.0:0 Listening
System4 TCP xxx.xxx.xxx.74:138 *.*
System4 TCP xxx.xxx.xxx.74:137 *.*
war-ftpd.exe:3252 TCP xxx.xxx.xxx.78:21 xx.xx.xx.217:33417 Established
webxserv.exe:2972 TCP xxx.xxx.xxx.78:80 0.0.0.0:0 Listening

While I was getting this information, the following showed up in the list:

[System Process]:0 TCP xxx.xxx.xxx.78:80 xx.xx.xx.217:32823 Time_Wait
[System Process]:0 TCP xxx.xxx.xxx.78:80 xx.xx.xx.217:32831 Time_Wait

The 2 lines above stayed for a couple of minutes and then disappeared.
0
 
sleep_furiouslyCommented:
OK, well it looks like IIS needs to be stopped ... for whatever reason it is still running.  Go to Services Control Panel and Stop WWW Publishing Service, then try starting your Apache server.
0
 
dyaroshAuthor Commented:
Did as you suggested and still could not start the Apache Service (same error).  Here is what I have now:

iisreset /status:

Status for World Wide Web Publishing <W3SVC> : Stopped
Status for Simple Mail Transfer Protocol (SMTP) (SMTPSVC) : running

TCPView:

alg.exe:396      TCP      127.0.0.1:1027      0.0.0.0:0      LISTENING      
inetinfo.exe:3684      TCP      0.0.0.0:25                      0.0.0.0:0      LISTENING      
inetinfo.exe:3684      TCP      0.0.0.0:1367      0.0.0.0:0      LISTENING      
inetinfo.exe:3684      UDP      0.0.0.0:3456      *:*            
lsass.exe:764      UDP      0.0.0.0:500      *:*            
lsass.exe:764      UDP      0.0.0.0:4500      *:*            
mysqld-nt.exe:1660      TCP      0.0.0.0:3306      0.0.0.0:0      LISTENING      
rdpclip.exe:372      UDP      0.0.0.0:1035      *:*            
svchost.exe:1000      TCP      0.0.0.0:135      0.0.0.0:0      LISTENING      
svchost.exe:1088      UDP      127.0.0.1:123      *:*            
svchost.exe:1088      UDP      xxx.xxx.xxx.74:123      *:*            
svchost.exe:1088      UDP      xxx.xxx.xxx.78:123      *:*            
svchost.exe:1136      UDP      0.0.0.0:1028      *:*            
svchost.exe:1136      UDP      0.0.0.0:1315      *:*            
svchost.exe:1248      UDP      127.0.0.1:1900      *:*            
svchost.exe:1248      UDP      xxx.xxx.xxx.78:1900      *:*            
svchost.exe:932      TCP      0.0.0.0:3389      0.0.0.0:0      LISTENING      
svchost.exe:932      TCP      xxx.xxx.xxx.74:3389      xx.xxx.xxx.240:2994      ESTABLISHED      
System:4                      TCP      0.0.0.0:445      0.0.0.0:0      LISTENING      
System:4                      TCP      xxx.xxx.xxx.74:139      0.0.0.0:0      LISTENING      
System:4                      UDP      0.0.0.0:445      *:*            
System:4                      UDP      xxx.xxx.xxx.74:138      *:*            
System:4                      UDP      xxx.xxx.xxx.74:137      *:*            
war-ftpd.exe:3252      TCP      0.0.0.0:21                      0.0.0.0:0      LISTENING      
war-ftpd.exe:3252      UDP      0.0.0.0:1046      *:*            
war-ftpd.exe:3252      UDP      0.0.0.0:111      *:*            
webxserv.exe:2972      TCP      xxx.xxx.xxx.78:80      0.0.0.0:0      LISTENING      
0
 
dyaroshAuthor Commented:
Thank you both for the input.  I changed the Apache httpd.conf file to Listen xxx.xxx.xxx.74:80 from Listen 80 and it now works.  Nopius - your explanation of what Apache was doing helped me see what was wrong in the Apache Conf file.  Sleep furiously - your suggestions taught me a lot that I will be able to use from here on out and I really appreciate the time and effort you put into this problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.