IIS Prevents Serv-U 7+ From Operating - KB Article #1715Related Articles --
There is a known conflict between Serv-U and Microsoft's Internet Information Services (IIS) application when both are installed on the same server and use the same port number (typically ports 21, 80, and 443). When configuring Serv-U, each domain can "listen" for connections on a certain IP address (or all IP addresses) assigned to the server and certain port number to receive incoming connections. This combination of IP address and port number is known as a socket. For example, by default Serv-U will listen for incoming FTP connections on all IP addresses on port 21, the default port for FTP. If there are two domains running on the same server (or two applications using port 21), an administrator may opt to assign two IP addresses to the server, and have each application listen on port 21 on a different IP address. Two network applications cannot listen on the same socket or they will conflict with each other.
Serv-U allows administrators to specify what IP address to listen on so that conflicts can be avoided, and it will only listen on those IP addresses if configured that way. However, even if IIS is configured to only use one IP address for a given website, IIS will still listen on all IP addresses, causing conflicts with other applications like Serv-U. Typically this behavior is displayed in either Serv-U showing a warning message in the Tray Icon, or IIS refusing to start properly.
Binding IIS6 to a Single IP Address
Because IIS does not allow administrators to easily configure it to only listen on certain IP addresses, Microsoft has made a Knowledge Base article available that describes how to override this default behavior and allow it to operate on the same server as other applications that need to use the same ports on different IP addresses. This article is available at http://support.microsoft.com/default.aspx?scid=kb;EN-US;813368. Once these steps are followed, IIS will properly use the IP addresses it is configured with and allow other applications like Serv-U to operate on other IP addresses.
Binding IIS7 to a Single IP Address
IIS7 uses a different method to bind to single IP addresses. To bind IIS7 to a single IP address, follow the method below:
- Click Start, type “cmd” in the search box then right-click cmd.exe in the Programs list and choose Run as Administrator. Click Continue on the UAC prompt
- In the command prompt type the following:
- netsh http show iplisten" (without the quotation marks). The list should be empty.
- In the command prompt type:
- netsh http add iplisten ipaddress=192.168.1.100 (replace 192.168.1.100 with the IP address of your machine
- Type out the show command from step 2 a second time and you should see your IP address in the list
- Reboot the IIS services by typing the following in your open command prompt
- Once IIS has reset close the command prompt and test both your IPs in a web browser again, this time IIS should only display on a single IP address