Well (sorry for the delay in responding, had actual work to do...), I have it set up 
to listen on a different port (per the MS/ISAServer.org setup instructions) and it 
appears that the new port number is then attached to the frame requests. For example, 
if I have IIS set up to listen on 8888 and route incoming requests to that port, 
my.server.com/exchange becomes my.server.com:8888 in the error messages that appear in 
the frames:

The page cannot be displayed 
There is a problem with the page you are trying to reach and it cannot be displayed. 

--------------------------------------------------------------------------------

Please try the following:

Click the Refresh button, or try again later.

Open the my.server.com:8888 home page, and then look for links to the information you 
want. 
If you believe you should be able to view this directory or page, please contact the 
Web site administrator by using the e-mail address or phone number listed on the 
my.server.com:8888 home page. 

10061 - Connection refused
Internet Security and Acceleration Server

--------------------------------------------------------------------------------
 

-----Original Message-----
From: Precht, David [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 11, 2002 1:53 PM
To: MS-Exchange Admin Issues
Subject: RE: OWA


Any errors / event ids ?


-----Original Message-----
From: Robert D. Young [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, June 11, 2002 14:20
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


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

Reply via email to