However, could you please help me in my 2 queries that i have asked in this forum. You can see those queries by name yatin_fredrick. One query is regarding SSL redirection using isa_redirects.zip and second query is with regards to OWA images not being cached on ISA server. I checked using cachedir command.
Any help or your thoughts would be much appreciated,
From: So cal
Wodnerful article! My company is doing something very similar with ISA 2004 publishing a NLB web farm. We had issues with using affinity and ISA always forwarding its internal IP address to the same web server instead of balancing the load. We had to turn off affinity on the NLB cluster and this seemed to fix our issue with this. Also we need all internal machines to hit the NLB cluster jsut like external users would, so the directions in this article clearly explained how to do this so thanks again for that extra bonus.
If i am understanding this article correctly will ISA 2006 be able to do NLB for published server that need NLB? does this mean that i dont have to run windows NLB on my internal cluster web servers?
Thomas, I wanted to bring something to your attention which I am not sure about. I followed this article in the past to setup OWA access however I was never able to implement the web farm properly (I reverted to using a host file on the ISA server and not publishing a web farm). We only have one Exchange server but plan to move to more in the future so it made sense to setup a web farm first.
I have since setup a duplicate test environment as we are moving to Exchange 2007 so I have been going through this all again. I have run into the same problem trying to publish the web farm in the test environment.
We are using split DNS as recommended. I was able to bring up the logon page but after typing in my credentials however once I click the logon button I received a "500 Internal Server Error" 1359.
I installed the ISA BPA and it pointed me towards the problem: "The original Host header is used but not defined, or it is defined but not used"
I followed the help and I had to do the following to my Advanced Farm Connectivity verification section: Type the URL used for server farm connectivity verification: https://*/ I had to specifiy https instead of http
Once I did this everthing worked OK, I was able to log into OWA.
I'm not sure if this is something that is specific to my environment but I thought it worth posting to help others in the future. Perhaps updating the article if this is relevant might help people out in the future as well.
Thanks very much, we do appreciate the articles you produce.