Re: Outlook Web Access problems with Linux Firewall

It's been a while but...if I remember correctly OWA has issues not
running on port 80 so I would redirect apache to port 8888 and leave
port 80 for owa...If this does'nt help then check with microsoft as I
am sure it is a known issue....

just checked with MS ...are you using https on that address? If not run
owa over https as it does not need port 80....then you should be
fine..on port 443

good luck
Oskar wrote:
Hello

I have a nasty problem, and i hope someone can help me.

In my company we have 20 win xp desktops with static IPs(192.168.1.x)
and
one Mail Server running Exchange with IP 192.168.1.100
They are connected with switches and at the front of all we have a
Linux Gateway that
has firewall capabilities using Iptables with 2 NICs.
This is the design

LAN------Switch-----Linux Gateway----ADSL Router------Internet
(192.168.1.X) (192.168.2.1) (200.X.X.X)


The internal eth1 interface of the Gateway has IP (192.168.1.102)
The external eth0 interface of the Gateway has IP (192.168.2.101)

In the router i have mapped all the ports to the Linux Gateway using
NAT,
so when somebody uses http://200.x.x.x the router redirects the
petition to
the Linux Gateway at port 80.
The Linux gateway also works as a web server using Apache (port 80).
The problem was that the mail server also uses port 80 for outlook Web
access.
Then my idea was to redirect petitions to port 8888 of the Linux
Gateway to Port 80 of the Mail Server(192.168.1.100) using Iptables and
the PREROUTING CHAIN.

That worked very well, people from the WAN can see the Apache Web
Server(Linux Gateway
running at internel IP 192.168.2.101:80) and the Outlook Web Access of
the mail server at
internal IP 192.168.1.100:80 through a redirection from
192.168.2.101:8888.

My problem is that when someone using a web browser from the WAN ,
types the address of the OWA, ie: http://200.x.x.x:8888/exchange they
get the OWA login screen,they put their username and password, and then
the outlook web access comes up, but with no inbox loaded..the frame of
the inbox and mails is not loaded..object request could not be found..
If i do this using http://192.168.1.100/exchange from the internal Lan
it works flawlessly..

any ideas?? is it a problem of the Linux firewall or with the exchange
mail server?

Thanks for your time

Oskar.

.

Relevant Pages

  • Re: Wierd 301 Moved Loop in OWA
    ... appears to be some sort of endless redirect loop. ... an HTTP connection for one certain item in ... a non standard port for regular HTTP and then the usual 443 port for ... OWA For WAP:www.leederbyshire.com ...
    (microsoft.public.exchange.admin)
  • RE: Changing SSL Port of OWA 2003
    ... I've been having a lot of problems with OWA on Exchange 2003 returning "You ... redirect to a URL, "/Exchange". ... > I have OWA with SSL, FBA and Front End schema and it is using an asp redirect. ... I need to change my SSL port ...
    (microsoft.public.exchange.admin)
  • Re: Outlook Web Access problems with Linux Firewall
    ... i have searched the internet and there is some problems with WebDAV and ... running on port 80 so I would redirect apache to port ... In the router i have mapped all the ports to the Linux Gateway using ... The problem was that the mail server also uses port 80 for outlook Web ...
    (comp.os.linux.networking)
  • Outlook Web Access problems with Linux Firewall
    ... In the router i have mapped all the ports to the Linux Gateway using ... The Linux gateway also works as a web server using Apache (port 80). ... The problem was that the mail server also uses port 80 for outlook Web ...
    (comp.os.linux.networking)
  • Re: Opening port 80&443 not only opens OWA but also Companyweb access?
    ... You don't need it for OWA -- 443 is all that's required. ... When I redirect the wan ports 80&443 to my sbs server, ... I think I dont want my companyweb displayed to the world. ... Maybe by redirecting OWA to a specific port? ...
    (microsoft.public.windows.server.sbs)