System kernel tying up port 80?
Hello, I'm running Windows 7 RC 64-bit and trying to setup WAMP, an Apache+PHP+MySQL distribution for Windows. Everything has installed fine and Apache was able to run after the install (I installed it some days ago), but today it wouldn't start. I digged through the logs and found it couldn't bind to port 80. I changed to config files to run on port 8888 and everything ran fine. So,interestedin what was running on port 80 I ran netstat -aon on the console and found this: Proto Local Address Foreign Address State PID TCP 0.0.0.0:80 LIVINGROOMDSKTP:0 LISTENING 4 I looked up that PID in the Task Manager and found that it was the System process and that really confused me. This is something that has onlyhappenedin the past few days. I installed the XP Modevirtualmachine today and that is the only thing I can think of that has changed in my system recently. I can connect to localhost on my browser and I get a white page, not a connection failed message, so something is accepting HTTP requests. If I try to connect from another computer on my local network, I do get a connection failed. So, either it only accepts connections from localhost or Windows Firewall is correctly blocking it. Does anyone have any idea what's going on? I don't want to jump to conclusions and assumesomethingmaliciousis happening right away, but the thought hasoccurred.
May 14th, 2009 5:31pm

Neil - No. IIS is not turned on by default. It can be installed as an additional feature. No idea what happened on your system to turn it on..
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2009 7:58pm

In my case it was SQL Server Reporting Services using port 80. TCP 0.0.0.0:80 PID 4. I installed SQL Server Express 2008 which included Reporting Services. I just stopped the service and set it to manual, I don't need it. Port 80 was released. That was on Windows 7 64bit.
February 4th, 2010 8:02pm

Thank you so much!!!
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2010 7:55am

Anyway, turning off Word Wide Web Publishing from the Service panel in the Control Panel fixed everything. I was tipped off when I saw inetpub in my C:\ directory and I recognized it as IIS. Thank you, Neil. This "fixed" my problem also. Sam
January 18th, 2011 11:43pm

In my case it was SQL Server Reporting Services using port 80. TCP 0.0.0.0:80 PID 4. I installed SQL Server Express 2008 which included Reporting Services. I just stopped the service and set it to manual, I don't need it. Port 80 was released. That was on Windows 7 64bit. This was the fix for me, thanks nz37. I also had IIS installed, which I initially assumed was the problem, but it wasn't, (kinda odd, as the default web site was set up on port 80, so they might've been conflicting anyway).
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2011 6:50am

Thought since many are having the same problem with the Port 80 busy as I and I am now on my 4th hour of trying to fix this after trying everything from the Skype BS to standing on my head and wiggling my ears, Finally got this to work. Could not find anything in the Task manager in the services or processes that was mentioned everywhere that was running so,............I hit the start button, typed IIS in the search programs and files, Well I'll B A SOB. A control panel I never seen before. Internet Information Services Manager came up. Under the actions panel on the left I hit STOP. Thanks Microsoft for not even mentioning this existed in the Help and Support on this machine. I am now going to take my shirt off ,climb on the roof of my home here in Alaska during this Blizzard with 80mph winds and beat my chest. Might even drop trow and point to the South as a salute to Billy for all my troubles. BTW: Windows 7 64 Problem XAMPP Control Panel, Apache won't start says Port 80 Busy 11/03/2011 Maybe this will help someone else
November 4th, 2011 12:15am

Yep, fixed it for me too.
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2012 7:16am

William, I noticed the same issue after IIS removed but Web deploy was left behind. Removing that fixed the issue, thanks for the heads up. Pat
October 10th, 2012 9:54am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics