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!
kbdaemonAsked:
Who is Participating?
 
kbdaemonConnect With a Mentor Author Commented:
SQL Reporting services listens on port 80 but does not identify itself as such. Just figured that out. If anybody else has this issue make sure you click on the advanced tab under SQL reporting manager to make sure you have switched the port <>80.
0
 
becraigCommented:
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.
0
 
kbdaemonAuthor Commented:
Thanks, but as I mentioned above that has already been done. Are there any other processes listening on TCP port 80 by default?
0
 
kbdaemonAuthor Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.