We have a Web Dispatcher in a DMZ (DMZ2) that is used for external (Internet) access to our E-Sourcing application. The E-Sourcing application is in another DMZ (DMZ1).
When external (sell-side) users enter the url in their browser to connect through the Web Dispatcher over the Internet, the initial E-Sourcing screen is displayed very briefly in the browser and then the message 'Page cannot be displayed' comes up on the screen. If the browser screen is refreshed, the login screen is then displayed and the user is able to log in with no issues.
This occurs only when trying to access the E-Sourcing application through the Web Dispatcher. It does not make any difference if the Web Dispatcher hostname is used in the url (internal access through Web Dispatcher) or if the url created specifically for the Web Dispatcher is used (external (Internet) access through the Web Dispatcher). The result is the same.
If either http://WebDisp_Hostname (internal) or http://www.myESOapp.here.com (external Internet) is entered in the browser, both display the front-end ESO screen briefly and then display the 'Page cannot be displayed' message. Refreshing the browser screen then displays the login screen and users can log in OK.
Can anyone point me in the right direction to solve this? I have reviewed the Web Dispatcher trace file and the E-Sourcing log file and can find no errors or anything that would indicate what might be going on. It appears to be a Web Dispatcher issue. Any help would be appreciated.
WL