M
Mark
Hi All,
A client has a 3rd party portal application that runs on port 80, I have
gone into IIS 7 and edit the bindings for the default website to run off a
different port. Restarted IIS / server and the Default website is indeed on
the other port, and Port 80 returns no page.
Checking into the server connections via Netstat it shows 80 as listening
but a "can not obtain ownership information" when trying to get the process
holding it open. Going one step farther, I got the PID for this port, which
was 4, the System and cannot seem to free up 80.
The problem I have is when I try to run the 3rd party app on 80 it does to
appear, I configure it for another port and it is fine.
Any Ideas? I know IIS 7 is a little different but I do not see any other
area to modify the port or is this the OS now holding onto 80 for whatever
reason?.
No Apache, SQL reporting services or anything like that on this server,
which I have seen interfere in other situations. I am scratching my head on
this one.
Any Ideas..???
A client has a 3rd party portal application that runs on port 80, I have
gone into IIS 7 and edit the bindings for the default website to run off a
different port. Restarted IIS / server and the Default website is indeed on
the other port, and Port 80 returns no page.
Checking into the server connections via Netstat it shows 80 as listening
but a "can not obtain ownership information" when trying to get the process
holding it open. Going one step farther, I got the PID for this port, which
was 4, the System and cannot seem to free up 80.
The problem I have is when I try to run the 3rd party app on 80 it does to
appear, I configure it for another port and it is fine.
Any Ideas? I know IIS 7 is a little different but I do not see any other
area to modify the port or is this the OS now holding onto 80 for whatever
reason?.
No Apache, SQL reporting services or anything like that on this server,
which I have seen interfere in other situations. I am scratching my head on
this one.
Any Ideas..???