Windows 10: Why Would/How Could Ports Refuse to Open?

Yes. That's what I've been doing all along. Constantly.
You don't believe me.
I can't show you on this machine but this machine won't work - that's what the whole thread is about.
But the other machine. I'll go switch it back on.
I'll create a rule 3300 to 80 on that machine.
I'll give you my IP and you can enter IP + port and you'll see that index page.

There, it's done.
IP is 101.167.174.244 Port is 3300

go for it. *Smile

 

DUH ... I totally misunderstood, sorry about that. You want it mapped that way ... lol ... I was thinking you wanted to use port 80 in the standard setup, which is what I always use. So, the only thing I can think of is to make sure port 3300 is added to firewall incoming rules or maybe some other process on that machine is using port 3300, both of which I think you've already checked *Sad

 

there's only one way my friend.....

p.s. I can't answer 'why/how the ports would refuse to open' beyond 'misconfiguration' which is so obvious it's really no answer at all.

but I can show how i fixed it - thanks to clues i found on the web - and the answer then becomes 'because this hasn't been done'.

and 'this' is having iis listen on 0.0.0.0 'add_iplisten'.

using netsh http

and then iisreset.

I was totally unaware of the netsh http tool. glad to know about it now. i'll help others by directing them to it.