![]() ![]() ![]() Prior to today a circuit was identified asįoreign Address:Foreign Port Local Address:Local PortĪssuming 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. IF the answer is will, can someone please explain basic TCP addressing as it is today. Well, many things WILL use that port or CAN use that port. 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? The things that makes me mad is, where does the system get off monopolizing that port with and administrator's ![]() And I can put IIS for what I do want IIS for, on another port. 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. 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īeen there since Win 7 (I don't think so. I'll try it, but doubt that it will work in this instance. Unfortunately, by default, and no way around this either as I can see is that Echo's Discover Devices command MUST use port 80. (I'm using HomeSeer for automation) it found nothing when on a WUP (Well Unknown Port - meaning I know it, the system shouldn't). The problem is I don't think that'll satisfy Amazon Echo. What I'll try is a NAT port translation from 80 to an internal port. I will try one thing, but if the System (PID 4) gets in the way, I'm getting rid of the system. And now I'm stuck with a web server I can't use on a WKP - and must NAt to a um. Or did MS just high-handedly decide, willy-nilly, that 80 cannot ever be used by us mere mortals trying to get work done. So, what's the configuration mistake that I made. but to a specific address and port on a specific Never. It's bound specifically to not to 0.0.0. ![]() System 4 TCPV6 80 0 LISTENINGĪnd my own webserver (behind my firewall) can NEVER open port 80. Yet, in running TCPVIEW from WinInternals.excuse me, SysInternals, I see this NO MATTER WHAT: I have killed Web Publishing service (apparently showed up in an update) and DISABLED it, too. I have killed firewall (I have another firewall) and disabled it as a service ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
May 2023
Categories |