Port forward HTTPS on 443 to IIS server doesn't work
April 30, 2011 5:06 AM Subscribe
An IIS web server won't respond to port forwarded requests from the world on 443, but will reply to port forwarded requests on port 80. The IIS web server will answer on 80 and 443 on the LAN. I tried a new router, as well.
posted by Runcible Spoon to Computers & Internet (6 answers total) 1 user marked this as a favorite
I have been helping a local non-profit, and they have an IIS (6?) webserver with a secure certificate that stopped responding to https requests that came through their router.
So I set up a new router, same problem (the first router had other issues, as well)
Port 443 was forwarded in each router to 443 on the IIS box
Port 80 works, on both routers
The IIS server will deliver a secure page over the LAN, however.
It will send it to a machine (my laptop) that isn't part of the local Microsoft domain. If I edit my local hosts file so that the local IP points to the domain name it will serve a page on port 443 with no complaint, or I can run the machine name and it will complain that the certificate doesn't match the name I'm asking for, but it will serve the page.
There are no entries in the web server access log of any requests on 443, even when requested locally
Running the IIS certificate test app shows no errors
If you enable SSL on the machine, then the page delivered at port 80 says it must be accessed securely, so that part works.
I have done several iisresets, as well
The only thing of interest I found in the event logs was a Userenv warning about unknown computers, but it provided no detail. It may be related to other services this box provides over the LAN
I saw a mention of this on google, someone else had the problem, but no answer was provided.
I know my way around Unix and Apache, but this IIS stuff is a whole different world (sighs)