Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have an installation of Windows Server 2008 running IIS 6 with a website listening on port 8080, even though I have moved the website to listen on 8080, port 80 is still kept in use by IIS (for truth by the kernel process : System - ProcId : 4).

I want to let another process listen on port 80 without uninstalling or disabling IIS, I want to keep IIS listening on port 8080 and another service on port 80, is there a way to do it?

I saw another similar thread here on serverfault but the solution (using httpcfg.exe delete iplisten -i 0.0.0.0:80 ) can work only in 2003 because in 2008 the utility httpcfg.exe doesn't exist and it seems that it cannot be installed ...

Does anyone have a solution to get rid of the kernel listening on port 80 in Windows Server 2008 with IIS running?

share|improve this question
    
Have you restarted the IIS Services ? If not you could try this ! –  Marco Jul 25 '13 at 20:52

2 Answers 2

Aleroot, go to c:\Windows\System32\inetsrv and then run the command "appcmd list site" ; this should give you a good starting point and list all the sites with their configs

c:\Windows\System32\inetsrv>appcmd list site SITE "Default Web Site" (id:1,bindings:http/:80:,https/:443:,net.tcp/808:,net .pipe/,net.msmq/localhost,msmq.formatname/localhost,state:Stopped)

SITE "Exodus" (id:2,bindings:http/*:8080:,state:Started)

share|improve this answer

Check IIS configuration to ensure that there isn't a website called "Default Website" running and listening on port 80.

If you stopped that website, you might still have to delete it, or put is on another port to free up port 80.

share|improve this answer
    
I've already changed the binding listening port of IIS bet still something listening on 80. –  aleroot Oct 15 '11 at 7:15
    
If you open a command prompt, and run 'netstat -o', you can identify the open port, and correlate it to a PID. You can then use Task Manager to identify the PID that is controlling this port. You might be surprised to find that it is not IIS. –  JohnThePro Feb 10 '12 at 22:58

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.