Externally, we want users to be able to connect to it via an external domain name of: jobs.fahc.org or jobs.fahc.fletcherallen.org. Both of these names are in extenal DNS and resolve to a dedicated IP on our ISA 2004 EE server for the jobs hostname.
The ISA Server is running dual-nics (one external, one internal). jobs.fahc.org (and jobs.fahc.fletcherallen.org) have a dedicated IP address of 192.240.46.61. A listener has been created just for this domain name/IP address, on port 80. No user authentication required, so it's been left at Integrated.
Here are the other params of the Web Publishing Rule I'm using: Action: Allow From: Anywhere To: fahc63.fahc.fletcherallen.org Forward the original host header [CHECKED] Requests appear to come from the ISA Server Computer [SELECTED] Traffic: HTTP Public Name: jobs.fahc.org, jobs.fahc.fletcherallen.org Paths: External path: <same as internal> Internal Path: /* Bridging: Web Server - redirect requests to HTTP port: 10100 Users: All Users Schedule: Always Link Translation: Replace absolute links in web pages [CHECKED] Content Types: HTML Documents, Images
HERES THE PROBLEM: When the user clicks on the Apply for Job (or any link), the javascript that is supposed to fire and take the user to the new page, doesn't seem to work. There are no errors displayed and nothing I can see in the logs that would indicate a problem. And nothing that stands out in the HTTP Headers.
It seems to me as if there is one MINOR thing that is not configured on Web Publishing Rule -- but it's killing me trying to find it.
_____________________________
A Hardesty Fletcher Allen Health Care Burlington, VT