Posted this problem to the Exchange thread last week, but it turns out this is where it needs to be. We have ISA sitting on a separate server in front of our DC/Exchange server. We were having problems with users in the same domain but on a different subnet than the DC being able to access the Exchange server through Outlook. The name of the Exchange Server and the mailbox coule be resolved fine through Mail Properties, but when Outlook was started, the user would get an "Exchange Server Unavaiable" message. After wrestling with this problem for the better part of a week, a guy who was consulting on this with me hit on the idea of removing the ISA Client from the offending computer. Turns out this was the problem and Outlook worked perfectly after. It was definitely some component of the ISA Client that was the problem, because if it was reloaded, Outlook would crap out again. (Incidentally, this wasn't a problem when we had ISA sitting on the same server as the DC/Exchange Server. It's only when we moved it off, in order to make RRAS work, that we had the problem).
There's nothing on this problem on Technet, and removal of the ISA Client is not a workaround I'm particularly happy about. There are serveral functions of the ISA Client that I really want, but can't use if people can't get their e-mail. Has anyone else run into this? Me: We need a better backup system.
My boss's boss: Backup? We don't need no stinkin' backup!
There's nothing on this problem on Technet, and removal of the ISA Client is not a workaround I'm particularly happy about. There are serveral functions of the ISA Client that I really want, but can't use if people can't get their e-mail. Has anyone else run into this? Me: We need a better backup system.
My boss's boss: Backup? We don't need no stinkin' backup!