Here's the scenario (please read this and not just the title, this is not an application setup issue):
- The application works fine over 80 (http) and 443 (https) from the public-facing IP address.
- From the internal IP address, we can only access the port 80 (http) side and the 443 (https) side gives a 'page not found' error.
- In IIS Manager, under Actions > Browse Web Site, it links to the public IP address over 443, not to the internal.
Why is this? Is this by design? We have confirmed that it is not an internal network setting prohibiting access over 443 (remember that it works fine on the public IP address, which is the one that counts anyways - but trying to figure out why this is).