Previous Next

• 10-02-2008, 9:46 AM

  Sham17 Joined on 10-02-2008, 9:34 AM Posts 5

  Cannot run default website on port 80 because of another process Reply Contact  I am trying to run the Default Website using port 80, but every time I try to start it I get a message saying that another process is using the file. I have 5 external IP addresses and the only process using port 80 is set to a different IP (I have listed them all to check). If I set the TCP port on the Default Website to another value (e.g. 81) there is no problem. I have used httpcfg.exe to list all the IP addresses and set disablesocketpooling to true.  I am on a server running SBS 2003 which someone mentioned could be a problem.  I need port 80 to run Outlook Mobile Access and the existing process on port 80 is run by an external company who also cannot (or will not) use another port. Their literature indicated that having multiple IP addresses would get around any problem.  Many thanks in advance to anyone who can help or point me in the right direction

• 10-02-2008, 11:06 AM

  In reply to

  mtg169 Joined on 10-02-2008, 2:33 PM Posts 7

  Re: Cannot run default website on port 80 because of another process Reply Contact You are assigning the site an IP address and not using "All Unassigned" correct? I know if you have other sites running, you must assign additional sites an actual IP. If you use "All Unassigned" you'll get errors stating port 80 is already in use when trying to start the site if another site is already using "All Unassigned".

• 10-03-2008, 4:12 AM

  In reply to

  Sham17 Joined on 10-02-2008, 9:34 AM Posts 5	Re: Cannot run default website on port 80 because of another process Reply Contact Thanks for replying.  Both websites have been assigned (different) IP addresses, and they also have host headers. I have searched extensively on the web and on Microsoft's site for an answer to this. As far as I can see it should work. I wondered if anyone had experience of SBS, and if that caused a problem.

• 10-03-2008, 4:15 PM

  In reply to

  murtaza_t Joined on 09-12-2008, 12:22 AM Earth Posts 126	Re: Cannot run default website on port 80 because of another process Reply Contact Remove the host header entry of both the sites.. it should do the trick. Moosa. --------- eUKhost.com Your Search for Webhosting Ends here.. ASP .NET - MSSQL Hosting Free ASP .NET - MSSQL Solutions

• 10-03-2008, 11:01 PM

  In reply to

  steve schofield Joined on 06-10-2002, 4:54 PM MI Posts 2,550

  Re: Cannot run default website on port 80 because of another process Reply Contact I'm not familiar with SBS.   Have you checked a SBS forum? http://technet.microsoft.com/en-us/sbs/bb839595.aspx I'm not sure you need to use httpcfg.exe since port 80 binds to all IP's by default, in regular IIS versions anyway. Steve Schofield Windows Server MVP - IIS http://weblogs.asp.net/steveschofield http://www.IISLogs.com Log archival solution Install, Configure, Forget

• 10-06-2008, 9:30 AM

  In reply to

  Sham17 Joined on 10-02-2008, 9:34 AM Posts 5

  Re: Cannot run default website on port 80 because of another process Reply Contact Thanks for the replies.  I now cannot access any website on IIS with port 80, including the one put there by the external company. If I use netstat to investigate ports, there is something listening on the IP that the external company use. They, however, take the view that it isn't their problem. I'll continue to hassle them and searching on the SBS forum

• 10-06-2008, 9:59 AM

  In reply to

  steve schofield Joined on 06-10-2002, 4:54 PM MI Posts 2,550	Re: Cannot run default website on port 80 because of another process Reply Contact Turn off IIS and see what process are using port 80. Steve Schofield Windows Server MVP - IIS http://weblogs.asp.net/steveschofield http://www.IISLogs.com Log archival solution Install, Configure, Forget

• 10-06-2008, 1:39 PM

  In reply to

  nathand Joined on 10-02-2008, 7:19 PM Posts 6	Re: Cannot run default website on port 80 because of another process Reply Contact I think httpcfg is your answer.  Here is some more details: http://technet.microsoft.com/en-us/library/cc781601.aspx Basically, use httpcfg set iplisten to set what ipaddresses you want IIS to use. If you don't use this to set an include list of ips, IIS will try to bind port 80 on EVERY ip address on the machine.

• 10-07-2008, 6:36 AM

  In reply to

  Sham17 Joined on 10-02-2008, 9:34 AM Posts 5

  Re: Cannot run default website on port 80 because of another process Reply Contact Thanks for your replies again.  I have got all of the IPs listed using httpcfg, and I have checked using listen that they are all there. I can also see them using netstat to look for ports in use. I have searched for processes using port 80 with netstat, and there is one: using the IP address in our range we have assigned to the external company. Initially this connected to an external IP which I tracked down to a hosting/communication company which I guess came about when the people we used were logged on remotely. I have the PID of the process but cannot find how to link that to an actual process. I shut down the programs associated with the external company (tricky to do for long as we lose our web link where people can apply to us online), and got the websites on IIS started using port 80. However, when I tried to log onto our system using remote web workplace I couldn't until I set the port on the default website back to 81.

• 10-30-2008, 10:18 AM

  In reply to

  Sham17 Joined on 10-02-2008, 9:34 AM Posts 5	Re: Cannot run default website on port 80 because of another process Reply Contact Just to update: the problem was that all of the possible IP addresses were set using httpcfg, including the one that was listening to port 80 for another process. Once I realised the same IP address was being used twice and deleted it from httpcfg, everything was fine.