SYMPTOMS
========
When you launch IIS 6.0 on a .NET Server machine, IIS binds to all IP
addresses on the server, not just the IP addresses that are assigned to
Web sites. If you then attempt to launch an additional application that
makes use of port 80 it will fail.
If an application is already using port 80 on any IP address and you then
attempt to start a website on port 80 on a separate IP address you will
receive the following error message:
"The process cannot access the file because it is being used by another
process."
CAUSE
=====
When IIS 6.0 is started and a website is enabled on port 80, http.sys binds
to port 80 on all IP addresses of the machine - represented by 0.0.0.0:80.
Once this has happened no additional processes can bind to port 80 on any
IP address.
RESOLUTION
==========
The current workaround is to use httpcfg.exe to manually instruct IIS6 to
bind to only one particular IP instead of binding to 0.0.0.0:80. This can
be done with the httpcfg.exe utility which ships with the Windows.NET
Server Support Tools. The steps are as follows:
1. Install the Windows.NET Server Support Tools
2. Open a command prompt and navigate to the directory with httpcfg.exe
3. Configure http.sys to STOP listening to all IPs: httpcfg delete
iplisten -i 0.0.0.0
4. Configure http.sys to listen to ONLY the specified IP:
httpcfg set iplisten -i <ip address>
6. Stop the HTTP driver:
net stop http
7. Stop the other service/process attempting to bind to port 80
8. Restart HTTP and any web services: net start "World Wide Web Publishing
Service"
9. Restart the service/process that also wants to bind to port 80
Thank you,
Tony DeVere [MSFT]
Microsoft IIS
Newsgroup Support
tdevere.RemoveThis@online.microsoft.com
"Please do not send email directly to this alias. This is our online
account name for newsgroup participation only."
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.
FAQ
Profile
Private Messages
Log in
