Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, November 25, 2016 2:23 AM
This is not acceptable.
I have killed firewall (I have another firewall) and disabled it as a service
I have killed Web Publishing service (apparently showed up in an update) and DISABLED it, too.
Yet, in running TCPVIEW from WinInternals..excuse me, SysInternals, I see this NO MATTER WHAT:
System 4 TCP 0.0.0.0 80 0.0.0.0 0 LISTENING
System 4 TCPV6 [0:0:0:0:0:0:0:0] 80 [0:0:0:0:0:0:0:0] 0 LISTENING
And my own webserver (behind my firewall) can NEVER open port 80. Never. It's bound specifically to not to 0.0.0.... but to a specific address and port on a specific
So, what's the configuration mistake that I made. Or did MS just high-handedly decide, willy-nilly, that 80 cannot ever be used by us mere mortals trying to get work done. And now I'm stuck with a web server I can't use on a WKP - and must NAt to a um... Well Unknown Port?
I will try one thing, but if the System (PID 4) gets in the way, I'm getting rid of the system. What I'll try is a NAT port translation from 80 to an internal port. The problem is I don't think that'll satisfy Amazon Echo. When telling it to Discover Devices (I'm using HomeSeer for automation) it found nothing when on a WUP (Well Unknown Port - meaning I know it, the system shouldn't). Unfortunately, by default, and no way around this either as I can see is that Echo's Discover Devices command MUST use port 80. That's nice. But I can't use port 80. So... There ya go. I'll try it, but doubt that it will work in this instance. Let's say that I'm not even connected to the Internet AT ALL, I STILL wouldn't be able to use port 80.So what did I do wrong (or has it always been there since Win 7 (I don't think so. I went from 7 to 10 (ugh) and it was OK at the time in 7 - reason I know is because I was moving at the time and needed IIS for access to certain things to make my move smooth.
Still doesn't matter. There has to be a way to use it. I don't want IIS for this. And I can put IIS for what I do want IIS for, on another port. The things that makes me mad is, where does the system get off monopolizing that port with and administrator's say so? Did I miss something fundamental, a change in policy that simply says all ports belong to the system and I can't use them?
All replies (3)
Sunday, November 27, 2016 5:26 PM
As this related to Windows 10, I suggest you discuss this in the appropriate Windows 10 forum found @
https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
Sunday, November 27, 2016 6:18 PM
Port 80 is not used by the system.
Many things will use that port, example; Web Deployment Agent Service, World Wide Web Publishing Service, SQL Server Reporting Services.
See Port 80 is being used by SYSTEM (PID 4), what is that?
Check those for possible culprits and for trouble shooting advise. Common issue it appears look at those threads.
Tuesday, November 21, 2017 9:28 PM
Well, many things WILL use that port or CAN use that port. IF the answer is will, can someone please explain basic TCP addressing as it is today. Prior to today a circuit was identified as
Foreign Address:Foreign Port Local Address:Local Port
Assuming we are local, there now has to be something in a Listener I MUST use (that is, if the answer is WILL use those ports, there are indeed ways within the TCP SYN to designate more information than a knock knock open up. Because it is the listener that ultimately passes an available port to the process that will be communicating because of the incoming SYN. Thus, the SYN ACK in which the LOCAL PORT (now no longer 80) is returned. At this point a circuit is complete and NEITHER side really using port 80. At this level there is no equivalent to a snap or even more accurately smaller than port. It can only be listener because unless something has changed, that half open isn't open. If the additional information IS being used in the SYN than only ONE listener (at a time on a single port) may be used because of the availability of the port. Once the SYN ACK is created (or the local port determined), port 80 is once again being listened upon.
We've seen the shortening of the life of addresses - at least public - so that the Address side is larger. Has that now happened to ports. Is there some extension of ports I know nothing about and seem silly asking? Or are the additional components of a SYN being used to tell wise listner that this SYN forwards or starts this process and that SYN does the same with a different process, in which case, I want it cut out. I don't want that.
But as I said, I work around a LOT of MS nonsense or MS opaqueness by using my own listener in front of an MS box.
Note to Mr. Happy... I've investigated all of those and tried all of those things. As I said, so far, nobody has said, this is how and where port 80 is confiscated. It's not any one process, although it should be a listener. And it can be a SPECIAL listener for all I care on port 80. But it is ONE process and I can't find it or get to it or find ANYBODY who can explain it. The tricks in those previously worked. You could then run whatever you want. I now think, though nobody has said so, that you no longer have a choice and everything, at least on port 80, must run as a process under some configuration of Internet Services. And I'd be happy with that if I knew how it directed one to ABC process and another one to a totally different process.
Joseph Tappe
Now on 2016 Server Essentials - same thing.