anonymous
Mon Sep 13 08:24:28 CDT 2004
Mark - Thanks, am aware of all the holes poked in our DMZ
and am working on that for the future, but not an option
at this time...all OWA to E2K users works fine and it
still failed from the inside.
>-----Original Message-----
>On Sun, 12 Sep 2004 07:38:54 -0700, "Steve Bevilacqua"
><steve@alston.com> wrote:
>
>>I recently performed an inplace upgrade of our front end
>>owa server from W2K/E2K to W2K3/E2K3 SP1. All E2K
>>mailboxes can access OWA fine. I then built a new BE
E2K3
>>server. E2K3 users can access OWA fine directly to the
BE
>>E2K3 server via
http://exchservername/exchange, but when
>>they try to connect via FE server via https, they
>>immediately get a "HTTP 400 Bad Request error" Looks
like
>>the request never even leaves the FE server.
>>
>>The OWA server is in a DMZ and port 80 is fine. I even
>>tried moving the OWA server to the inside with the same
>>results.
>>
>>Any thoughts?
>>
>>Steve
>
>The FE shouldn't be in the DMZ since it requires way more
than tcp 80
>to be open. What else is open?
>Better will be to abandon troublseshooting this and place
the FE on
>the internal network and publish tcp 443 from the
Internet through to
>the FE. If you want something in the DMZ then use an ISA
server. There
>are good instructions for setting up ISA and an FE at both
>www.mexchange.org and www.isaserver.org
>.
>