Calling MS Admins: ISA 2004
 

Ok.
We have an unstable ISA 2004 gateway, it keeps folding for no good reason. I shall call it ISA2. A new one has been built from the ground up using the latest MS version of ISA server 2004 I shall call it ISA3. On ISA3 The VPN, SMTP and other access rules are fine, however the Outlook Web Access rule does not work. The port 80 and 443 traffic is forwarded to the Server 2000 / IIS / Exchange front end server, but while this works on the old one (ISA2) it does not work on the new one (ISA3). The major difference between the 2 IS servers is the first one (ISA2)was built copying the config from a previous ISA server(ISA1), and the new one (ISA3) was built fresh from the ground up in case ISA2's instability was a config issue carried accross from ISA1. It's entirely possible we've missed a setting somewhere but any thoughts?

Edit: External web connections to the Server result in an error 500, presumably handed on from IIS on the Exchange front end server?

erm, i'm sure i could make more sense of someone speaking latin! :lol:

Re: Calling MS Admins: ISA 2004
 

Is the answer 32?

is it george best?

blue.....er.....no red......AAAAGGGGGGGGGHHHHHHHHHHHHHHH

Sorry I don't understand a word of that.

Q1 what version of linux are you using
Q2 MS!!... WTF don't you know anything about computers.

If answer to Q2 is yes then you obviously don't work for MS

Cheers guys keep them comng.... Obviously I got to choose the entire infrastructure and recomended ISA server... Not! None the less you works with what you got....

Tim: Having visited a few Linux sites in my time I recognise your point that no one EVER has problems with Linux... :roll: :lol:

Filtering out all the historical waffle. You want to know why the OWA front end box isnt working through the ISA box?

Give us what you've got configured already.

Pretty much. Sorry about the waffle this has just been doing me in...
The ISA server has a web publishing rule pointing to the IP address of the Outlook frontend server running IIS. This uses forms based Authentication and works on Ports 80 and 443. This apprears to be how it is set on the old one, and yet it doesn't publish the OWA welcome page. Please let me know what details you would like and I'll try and get them for you.

Whenever facing a problem like this under linux, I do the following:
1) Output the full config to a file for each server/daemon.
2) diff the files.

Surely this can be done in MS, or is MS proving itself inadequate yet again? I know a win32 version of diff exists, so it's just a matter of spitting out the configs.