After following the guide, I get this error when trying to connect to my OWA:
Technical Information (for Support personnel) Error Code: 502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL). (12202) IP Address: 10.10.x.x Date: 10/18/2004 1:43:13 AM Server: ISA.Amherstburg.local Source: proxy
If I connect to OWA from the ISA server, it works successfully.... I dont get it myself, tripple checked the settings, same error
On my Logging Tab, I have:
Denied Connection by Default Rule, Client Name: anonymous
How does your config deviate from the recommendations in that article? One danger sign I see already is that you're using an illegal TLD for the name of your ISA firewall.
Nicely done. This is a little off topic but a recurring bother for me. How do you print the "printly friendly" versions of these articles? No matter what I do with margins, most of the articles (including this one) simply do not fit on portrait 8.5X11 paper. Sentences are truncated.
Funny you should mention that, as I noticed the exact same thing yesterday when I was playing with the site.
The problem is that some of the figures are too wide for the page. Since I'm no web programmer or graphic designer I have no idea how to deal with the problem. When I've tried to resize the pics, they end up looking like caca
If you want to print out the article, I'd be happy to send you the Word .doc. Just send me a note at tshinder@isaserver.org
Well mine is a bit different, my ISA Server is a member of my internal domain, which is a different domain name than my public name.. I know this is not recommended, but it is the way it is set up here, We have DNS Servers for our internal and external domains, so internally we can access the OWA site, and externally.
Even though you have different domain names, you still must create a split DNS infrastructure to make things work. And the next time you set up a new network, remember NEVER USE the .local domain EVER!
Even though you have different domain names, you still must create a split DNS infrastructure to make things work. And the next time you set up a new network, remember NEVER USE the .local domain EVER!
I'm writing the publishing chapter in the book this week, and will go into long detail on setting up split DNS for a well designed domain infrastructure, and a bootstrap method for situations like yours, where you kind of snafu'd the domain name, but can still get you up and running with a split DNS.
well im getting somewhere, Now it says that the Certificate chain was not from a trusted authority. I must not have imported my Cer. right... Ill try that step(s) again..
Posts: 6
Joined: 14.Oct.2004
From: New Zealand
Status: offline
Hi Tom
Got a question regarding using the ISA OWA FBA. If I select to block all attachments here, then is that final, ie it does not matter if the Exchange Server is set differently on how to handle attachments of Level 1/Level 2 file and mime types.
Any chance in the future, that an option will be available to only enable attachments in one direction, being able to open attachments, but not being able to send attachments?
i've managed to publish OWA using this article and it works, but my OMA doesn't . Do I need a seperate rule for publishing OMA as well ? Is there an article of this available ?
Got a question regarding using the ISA OWA FBA. If I select to block all attachments here, then is that final, ie it does not matter if the Exchange Server is set differently on how to handle attachments of Level 1/Level 2 file and mime types.
Any chance in the future, that an option will be available to only enable attachments in one direction, being able to open attachments, but not being able to send attachments?
RajiA
Hi Raji,
Not at this time, but you might want to put it in the Wish List section.
Thanks for an excellent step-by-step guide. This has been really helpful.
However I do have a problem, that you might be able to help with.
I have followed your guide pretty much to the letter, and it seems to work fine for clients on the internal network. However, when clients from the external side log on to the OWA site, they get forwarded to the url "https://mail.domain.com/CookieAuth.dll?Logon" and see the follow text in th browser:
-------------------- Unknown Request The request could not be resolved by the server. --------------------
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA Server 2004 General ] >> Exchange Publishing >> Discussion about article on Publishing OWA using ISA Firewalls 
Discussion about article on Publishing OWA using ISA Fi... - 
![[Confused]](/image/smiles/confused.gif)
![[Smile]](/image/smiles/smile.gif)
I have no idea how to deal with the problem. When I've tried to resize the pics, they end up looking like caca ![[Razz]](/image/smiles/tongue.gif)
RE: Discussion about article on Publishing OWA using IS... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread