Bradey Honsinger
2005-Jan-04 00:00 UTC
RE: Outlook Web Access behind shorewallfirewalldoesn''t work
Tom Eastep wrote:> On Mon, 2005-01-03 at 15:22 -0800, Boyd Kelly (Coast Systems) wrote: > > Thanks for such a quick reply Tom! > > > > Any suggestions then as to what I might do other than > putting a second > > nic in the SBS and opening it up for web access? I don''t > like the idea, > > but since MS SBS includes fireall that is actually what MS > suggests. > > I have no suggestions -- possibly someone else on the list is familiar > with this issue.We''re running this setup, with Exchange 2003 behind a Shorewall firewall--the new OWA interface is indeed an improvement over the old one. We redirect only HTTPS from the firewall to the box running OWA, and it works fine (new interface and all). Redirecting HTTP would be equivalent. No other ports are required. I suspect this is entirely a proxy server issue, as hinted at in the article snippet you included. Shorewall has nothing to do with HTTP verbs, as Tom stated, but a proxy server may. The article also described several other potential causes which aren''t proxy-related--I''m sure you''ve tested this already, but does it work properly from a client machine on the local network, within the firewall? - Bradey
Possibly Parallel Threads
- RE: Outlook Web Access behindshorewallfirewalldoesn''t work
- Using private & public addresses together i n the Shorewall''s DMZ zone
- Forcing ISP ARP cache to refresh immediately
- RE: Outlook Web Access behind shorewall firewalldoesn''t work
- Outlook Web Access behind shorewall firewall doesn''t work