asked on

setting up IIS 6 for port 81 (Server 2003)

I am moving IIS to port 81 and setting up Apache 2.4 on our server to handle our main site while IIS will handle the apps. No issues with Apache because it is NOT installed yet, this is purely a Windows issue. I have configured IIS Manager site properties to listen to 81 only. I have even tried setting IIS via "httpcfg set iplisten -i" - and that was successful because "httpcfg query iplisten" yields this:

C:\>httpcfg query iplisten
IP : 192.XXX.XXX.6:81
-----------------------------------------------
IP : 192.XXX.XXX.2:81
-----------------------------------------------

but "netstat -aon" yields this:

Proto Local Address Foreign Address State PID
TCP 192.XXX.XXX.6:80 0.0.0.0:0 LISTENING 4
TCP 192.XXX.XXX.6:81 0.0.0.0:0 LISTENING 4
TCP 192.XXX.XXX.2:80 0.0.0.0:0 LISTENING 4
TCP 192.XXX.XXX.2:81 0.0.0.0:0 LISTENING 4

any ideas for figuring out AND stopping/moving the process staying on port 80? PID 4 is "SYSTEM" by the way.

Thanks!

becraig

Open your IIS >
right click on web site in question
Properties
Web Site Tab
Advanced..
Change the host binding here, or simply delete the site if you do not plan to use it.

kbdaemon

ASKER

Thanks, but as I mentioned above that has already been done. Are there any other processes listening on TCP port 80 by default?

ASKER CERTIFIED SOLUTION

kbdaemon

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kbdaemon

ASKER

I hope anyone else struggling with IIS port reassignment on Windows Server who also have SQL running will benefit from my frustration on this. SQL, despite being a separate piece of software, will NOT identify itself on the port usage command ("netstat") so if you have IIS configured correctly but still see a problem then check out your SQL settings.