This article explains that IIS 6.0 and apache cannot use port 80 at the same time.

Apache and IIS servers are now widely used Web platforms. IIS 6.0 servers can be used independently as a Web server or together with compatible tools, it can be used to establish Internet business, access and operate data from different data sources, and create Web applications. These applications use server scripts and component code to complete some client-server functions.

The latest information can be found on the IIS server Web site. You can also find some helpful information from the Server area section of the MSDN Online Web Workshop content table.

IIS 6.0 is closely integrated with Windows NT servers. It ensures that network administrators and application developers have the same security, network, and management functions as Windows NT servers.

We installed IIS 6.0 and apache on the local machine for the debugging program, but we cannot use port 80 at the same time. Below, we will explain the solution for you:

IIS5, coexistence under multiple IP addresses, IIS is 192.168.0.1, apache is 192.168.0.2 original address
 

 
 

  
  
C: \ Inetpub \ Adminscripts cscript adsutil. vbs set w3svc/disablesocketpooling true
  
  
The command returns the following disablesocketpooling: (BOOLEAN) True
 
 

Restart IIS 6.0

Inetpub \ AdminScripts> cscript adsutil. vbs set w3svc/disablesocketpooling true

Because DisableSocketPooling is defined as a valid attribute in the IIS 6.0 metabase architecture (MBSchema. xml), you can still set this attribute using Adsutil. vbs, but this setting does not work. Features in IIS 6.0 are part of the new core-level driver HTTP. sys. To configure HTTP. sys, you must use Httpcfg.exe.

Here, we have solved the problem of IIS 6.0 and apache.