New
#1
Why Would/How Could Ports Refuse to Open?
Not sure where this belongs but it certainly could be a networking question.
I port forward on the router so's web traffic can access my IIS installation on one machine on my LAN.
But the ports never open on this machine. No traffic gets in. No port checker reports the ports as open.
Other machines on the LAN I can forward to without a problem. So it's not the router
So it's not the ports on the router, the 'wan' port. So it must be the ports on the local machine.
Where are these ports? In ROM? or in RAM? How many are there?
I wonder if it could even be a hardware problem, see.
Unlikely, because port checkers report port 80 as being closed. But it can't be closed if my browser traffic is working, and it is.
But I wonder anyway.
What processes in win10 can influence whether a port is open or not?
In case it was IIS I have 'upgraded' my win10 installation with that upgrade where you go to the web and download from MS and then run it and choose upgrade - keep files and apps.
It didn't help. So now I wonder about it. It carries on, takes so much time, as though it is a total reinstall of win10 and that's what I thought it was. But is it?
Looks like it has left some part of the OS behind that interferes with the ports.
What part of the OS returns 'pings' ? Refuses pings? I got a message one time said the ping was refused.