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 guess there must be a logical explanation for this.Įdited by Mis3ry99, 27 July 2021 - 03:29 AM.I have killed firewall (I have another firewall) and disabled it as a service On a side note, even though when I'm offline, my antivirus program (according to the PID)uses a remote connection to a foreign ip using port 443 and it is the only connection being shown by PortExpert in that scenario. My understanding about this process is very limited. Not sure how to feel about the svchost connections though. So I ran through each single PID and I found out that they were all tied to either my antivirus program, it's PC booster program, VPN and the likes or svchost. After restarting PE the connection showed up again alongside multiple processes that were using port 80 as well. A shame because I wanted to further review the Windows® connection I initially thought, but it got even better. I hope this was just a coincidence due to the shutup10 changes. Then I deactivated a ton of stuff in shutup10.Īfter reconnecting to the internet, PortExpert magically closed without warning. I disconnected from the internet and ran the adwcleaner and all it found was a web companion from lavasoft that was supposed to protect me while surfing, so my guess is that this was a false positive.
0 kommentar(er)
