We ran into that after checkpoint required that we put in an anti-nimda rule into the firewall (even though the requests were blocked by other rules). We were having an issue with a cvp server and they wouldn't even look at it without us having that rule.
Basically OWA uses calls that trigger their nimda rule. -----Original Message----- From: Robert D. Young [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 2:20 PM To: MS-Exchange Admin Issues Subject: OWA Hi all. I'm trying to get OWA working for the first time on my W2K/E2K system (worked fine for years on my NT4/Ex5.5 boxes) and have run into a bug someone may be familiar with. Environment: Clients are W2K/IE6 with current patches (lat time I looked). Server is W2K AS, E2K SP1, ISA (yes, on the same box) and IIS 5 (basically, BO2K). I've followed all the ISA/Shinder/Technet stuff I can find to config so local IIS listens on a free port and all requests are redirected to that port. Can get to in-house written publicly-available web pages on the system from across the Internet fine. I can access OWA in-house but across the net I am requested to sign in (OK), then I get the two frames and a long pause. Eventually, both frames get a "page cannot be displayed" message in them. Any ideas? - Robert List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm