Here is the environment:
1 Server, only server in the forrest, running Win2K as AD forest root DC with Exchange 2000 back-end and OWA on a private (internal 172.16.x.x) network.
Firewall that does NAT between this network and the internet.
Two external IP addresses, translated directly two two internal addresses. For external DNS lookups, i.e. WM.SomeCompany.Com, both ports 80 and 443 are open to the "second" site which has only an HTML/js redirect page to the OWA web site. The OWA web site is accessable only via SSL (port 443). (to make life easier for the users, eh?)
Okay - I can use the encrypted (OWA) site from the internal network - using machines that are in the AD domain (apparently) without difficulty.
Externally, Internet Explorer redirects correctly. The SSL connection is established (cert-admin created certificate in use) and I am prompted with the OWA logon prompt (username, password, domain). After entering correct logon credentials, I am greeted with the 'ole HTTP 404 - File not Found error.
The redirected site is using the external side of the firewall's IP address, so the URL re-directed to is such like "https://220.127.116.11/exchange
If I THEN at this time ask my browser to access "https://18.104.22.168
", I am greeted with the generic IIS5 "under construction" page. If after THAT I re-enter the correct url "https://22.214.171.124/exchange
", the OWA client uses the logon credentials provided above and logs me in correctly.
I'm totally stumped.
TY VM for your help with this one!
Points will increase if this takes a long diagnosis to resolve!