This question is a question about a Windows Server configuration issue:

Configure IIS Web Site for alternate Port and receive Access Permission error

For some reason it was moved to Stack Overflow even though it has nothing to do with programming. On the same day it was closed as "off topic" by several people on Server Fault.

On Stack Overflow it survived for a few days with me repeatedly asking to move it back to Server Fault since it was not a programming question.

Then it was closed on Stack Overflow too, for being "off topic" (which I totally agree with).

I totally don't see why a question about a TCP port issue affecting IIS on Windows Server should be "off topic" on Server Fault.

And what's worse, I still have that problem and could really need an answer rather than a discussion about why I am not allowed to have the problem. Problems with IIS and TCP on a Windows Server ought to be on topic on Server Fault!

This question is a question about a Windows Server configuration issue:

Configure IIS Web Site for alternate Port and receive Access Permission error

For some reason it was moved to Stack Overflow even though it has nothing to do with programming. On the same day it was closed as "off topic" by several people on Server Fault.

On Stack Overflow it survived for a few days with me repeatedly asking to move it back to Server Fault since it was not a programming question.

Then it was closed on Stack Overflow too, for being "off topic" (which I totally agree with).

I totally don't see why a question about a TCP port issue affecting IIS on Windows Server should be "off topic" on Server Fault.

And what's worse, I still have that problem and could really need an answer rather than a discussion about why I am not allowed to have the problem. Problems with IIS and TCP on a Windows Server ought to be on topic on Server Fault!