4
Using Windows7 Home Premium. It's a development machine, but that shouldn't matter.
I have IIS installed and can browse to http://localhost websites from the local machine. The default website is set to use port 80.
I added another website to IIS, set it to use 32-bit app pools, and port 81. when I try to browse to it, via localhost, I get "No connection could be made because the target machine actively refused it 127.0.0.1:81"
ok, this is pretty easy, right? Just enable HTTP over port 81 in the Windows firewall, right? I figured to use the port-80 rule in the firewall as a pattern.
To my surprise, there is a port 80 rule in Windows Firewall, but it is not enabled. This is a snip from the Windows Firewall MMC:
Yet I am able to connect to localhost via port 80.
and I am not able to connect to localhost port 81.
WHY?
That's neat/weird. Do you have multiple nics or something? I've found IIS to be profoundly crazy when it comes to binding to ports. Still, this seems like weird behavior. Maybe you have some malware compromising your firewall? – James T Snell – 2011-08-10T15:34:58.573