OWA with ISA connection timeout with email attachment 10Kbytes

[Hong]

Windows 2003 SE SP1 with Exchange 2003 Server
ISA Server 2004 SE with SP2
OWA 2003

Consistent symptom of request timed out (expired page) while trying to
attach files greater than 10kilobytes for an outbound email from an external
OWA
client. Opening existing attachment of much bigger size (from inbound email)
has no problem

Connecting directly to the Internal OWA server via IE does not present this
error regardless of the attachment size, while passing through via ISA 2004
server this problem happened.

The pop-up message received in IE from the ISA server is:

---------------------------------
The page cannot be displayed
Explanation: The connection to the website was closed by the site or by one
of its servers.
Try the following:
Refresh page: Search for the page again by clicking the Refresh button. This
might have been a one time error.
Technical Information (for support personnel)
Error Code 10054: Connection reset by server
Background: When the gateway or proxy server contacted the upstream (Web)
server, the connection was ended by the upstream server.
--------------------------------

Typical connection syntax that works:

http://BE-servername/exchange
http://FE-Z999/exchange and/or https://FE-Z999/exchange

while consistently generating error 1054 with this syntax

https://<companyname>.webmail.intl.com/exchange (FE-Z999 via ISA)

Am new to ISA and wonder if the temporary space (cache) assigned to OWA
clients from Exchange server (default of 10megabytes) is used at all in this
mode i.e. connecting via the ISA server. Is there any interop setting between
ISA and the OWA/FE server?

Thanks for any troubleshooting idea

Hong

[Shijaz]

Hi,

- Are you using any kind of firewall chaining/proxy chaining on ISA server?
- Is your internal network IP range configured correctly in ISA (networks
--> Internal)?
- Did you follow the Microsoft procedure for publishing OWA with SSL?
http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/owapublishing.mspx

--
Shijaz
www.shijaz.com/isaserver

[Juan Muñoz]

In spanish version:
Configuration \ Network \ LAN \ Properties \ Proxy web \ Avanced Options

[clarkm]

Hong wrote on 06/15/2006 04:55 ET :
> Windows 2003 SE SP1 with Exchange 2003 Server
> ISA Server 2004 SE with SP2
> OWA 2003
>
> Consistent symptom of request timed out (expired page) while trying to
> attach files greater than 10kilobytes for an outbound email from an external
> OWA
> client. Opening existing attachment of much bigger size (from inbound email)
> has no problem
>
> Connecting directly to the Internal OWA server via IE does not present this
> error regardless of the attachment size, while passing through via ISA 2004
> server this problem happened.
>
> The pop-up message received in IE from the ISA server is:
>
>

> The page cannot be displayed
> Explanation: The connection to the website was closed by the site or by one
> of its servers.
> Try the following:
> Refresh page: Search for the page again by clicking the Refresh button. This
> might have been a one time error.
> Technical Information (for support personnel)
> Error Code 10054: Connection reset by server
> Background: When the gateway or proxy server contacted the upstream (Web)
> server, the connection was ended by the upstream server.
>
>

> Typical connection syntax that works:
>
> http://BE-servername/exchange
> http://FE-Z999/exchange and/or https://FE-Z999/exchange
>
> while consistently generating error 1054 with this syntax
>
> https://<companyname>.webmail.intl.com/exchange (FE-Z999 via ISA)
>
> Am new to ISA and wonder if the temporary space (cache) assigned to OWA
> clients from Exchange server (default of 10megabytes) is used at all in this
> mode i.e. connecting via the ISA server. Is there any interop setting between
> ISA and the OWA/FE server?
>
>
> Thanks for any troubleshooting idea
>
> Hong
>

I had this exact problem. This Microsoft technet post fixed it for me:
http://blogs.technet.com/b/benw/archive/2007/05/03/exchange-2003-isa-and-attachment-size.aspx

It comes down to an IIS setting on the OWA server called
"UploadReadAheadSize". The fix is a one line command like this:

To modify this parameter, run the following command:
C:inetpubadminscripts>adsutil set w3svc/UploadReadAheadSize "<Size in
bytes>"
---------------------------------