Knowledgebase:
How to Run IIS and IceWarp on the Same Server
Posted by Michael Filip, Last modified by Michael Filip on 08 August 2013 12:43 PM

How to Run IIS and IceWarp on the Same Server

Starting with version 10.1.2, the default port for Web service is 80 (HTTP) and 443 (HTTPS).

These ports are the same as Microsoft's Internet Information Service (IIS) is using. If you have only one IP address, you need to (1) change either IceWarp server or IIS to a different port, or if you have more than one IP address, you can (2) bind separate processes to those IPs.

1.      Running IIS on the different port than default

IIS7:

-          Open Internet Information Services (IIS) Manager.

-          Select the Web site that you wish to configure.

-          In the Action pane, click Bindings.

-          Click Add to add a new site binding, or click Edit to change an existing binding.

-          Change HTTP and HTTPS ports according your needs.

-          Click OK to apply the changes.

-          Restart IIS.

 ISS

 

2.      Binding IIS to different IP.

You should disable socket pooling on IIS. This is different for each IIS version.

IIS7 (Windows 2008/Vista/Windows 7)

Use the Netsh command. More info at: http://msdn.microsoft.com/en-us/library/ms733768.aspx 

 

IIS 6 (Windows 2003 Server)

To disable HTTP socket pooling you need a tool named httpcfg.exe which is available from the support tools on a Windows Server 2003 CD-ROM located in \support\tools\support.cab.


Open a command prompt and type: 

net stop http /y 

This stops all IIS services. 

Type 
 

httpcfg set iplisten -i IP:80 

Substitute the IP with the appropriate IP address where you want IIS to listen. 

NOTE: List the IP Addresses (with ports) that you want IIS to LOCK, not the IP that you want Icewarp's Web Server to use. 


A successful change will result in the following message being displayed: 

HttpSetServiceConfiguration completed with 0 

Now you can run another application on port 80 on different IPs other than you used for IIS. Sometimes, it will be necessary to reboot the server after this change but you can try to start IIS by net start w3svc 

Microsoft article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;813368 

To disable SMTP socket pooling you should run a command prompt, go to c:\IntePub\AdminScripts folder and run the following command: 

cscript adsutil.vbs set /smtpsvc/1/DisableSocketPooling true

 

IIS 5 (Windows 2000 Server)


Open a command prompt and browse to the C:\InetPub\AdminScripts folder. Then type:

cscript adsutil vbs set w3svc/DisableSocketPooling TRUE 
cscript adsutil.vbs set /smtpsvc/1/DisableSocketPooling true 

The first command disables HTTP socket pooling and the second one disables SMTP socket pooling. Reboot the server after that. 
Microsoft article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;238131
Microsoft article: http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;259349

3.      IIS redirection.

You can of course redirect the URL from IIS to running IceWarp server. To do that:

-          Open IIS Manager and navigate to the level (Site) you want to manage.

-          In Features View, double-click HTTP Redirect.

-          On the HTTP Redirect page, select Redirect requests to this destination. In the corresponding box, type the URL to which you want to redirect the request – your IceWarp server URL.

-          In the Actions pane, click Apply.

ISS

(2 vote(s))
Helpful
Not helpful

Comments (0)