03-21-2018, 12:22 AM
I am not sure you are understanding my question.
I understand that you can configure IIS and/or Intraweb to listen to specific ports, or listen to all ports. That is 100% clear. You said it many times.
However, my understanding is that once IIS is configured to listen to port 80 (as an example) it blocks other applications from listening to port 80. Thus, if you have IIS running on port 80, you need to have other applications on that same machine listening on other ports. Thus, if IIS is running on port 80, and you want to have other webservers listening on that machine, you have to have them use ports other than port 80. Which means opening up non-standard ports, which system admins dont like.
I understand you can configure Intraweb to listen to whatever port you want. BUT, if you have configured intraweb running as a windows service to listen to port 80 (via the servercontroller as you mentioned) does it block other applications from listening to port 80?
I understand that you can configure IIS and/or Intraweb to listen to specific ports, or listen to all ports. That is 100% clear. You said it many times.
However, my understanding is that once IIS is configured to listen to port 80 (as an example) it blocks other applications from listening to port 80. Thus, if you have IIS running on port 80, you need to have other applications on that same machine listening on other ports. Thus, if IIS is running on port 80, and you want to have other webservers listening on that machine, you have to have them use ports other than port 80. Which means opening up non-standard ports, which system admins dont like.
I understand you can configure Intraweb to listen to whatever port you want. BUT, if you have configured intraweb running as a windows service to listen to port 80 (via the servercontroller as you mentioned) does it block other applications from listening to port 80?