I have a customized web site that has been configured on a ND 6.5.4 server using Internet Site Documents and not Web Configuration Documents.
The site uses an NAT’d external address that corresponds to the static IP address configured on the server. The IP address is configured correclty on the Domino Server.
Within the application, we have configured a customized login page and this customized login page is configured within the DOMCFG. The form exists in the DB and is signed by an ID with the correct privs for design elements on that server.
In the Internet Site doc, the Session Authentication is set to Single Server.
When I connect directly from a web browser directly on the server that’s hosting the site, I am able to open the main page, navigate correctly to the link that should present the login page, click on the link and I see the customized login page.
That’s the good news.
The bad news is that when I try to access the exact same site from a browser that is external to the server using the NAT’s address, I can get to the same URL that should launch the customized login page but instead of seeing that custom login page, I only see the default Windows login screen.
The site works but the customized page is much more pleasing to the eyes.
Is the problem within the browser or in the Internet Site configuration? Is it network related? Is it something I haven’t thought of?
If I use http://www.myweb.com, directly from the server, I can get to the home page but I can’t launch the customized login form. It is in this scenario that I get the boring grey and blue Windows login pop-up.
Thanks … sorry for not being totally crispy on the first go.
In the Internet Site document, did you set just the internal ip address as the web site? You should have both the internal and external ip address, and the dns name there.
In domcfg.nsf, did you set the mapping to apply to “Specific Web Site/Virtual Server”, or “All Web sites/Entire Server”? If the former, you need to specify the internal and external ip address, and the dns name in this field too.
What the web server sends back to the browser depends on what is written in the address field of the browser. The browser requests content from the host name or ip address given in the url, and it tells the server which it is requesting content from. Therefor, a web server can deliver different content depending on the host name or ip address given.
If I use http://www.myweb.com, directly from the server, I can get to the home page but I can’t launch the customized login form. It is in this scenario that I get the boring grey and blue Windows login pop-up.
Thanks … sorry for not being totally crispy on the first go.
