Re: Outlook Web Access problems with Linux Firewall



i dont use https because for that you need a certificate from a CA..i
want just
a simpler way to enable this..

i have searched the internet and there is some problems with WebDAV and
firewalls
or proxy servers..if you have another solution that would be great!

greetings oskar



Radge ha escrito:

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

  • 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: Linux als Router
    ... # Enter all trusted network interfaces here. ... # which should be available to the internet and set FW_ROUTE to yes. ... space separated list of ports, ... # Packets to silently reject without log message. ...
    (de.comp.os.unix.linux.misc)
  • Re: SharePoint 3.0: problems with external access
    ... "Go to 'Alternate Access Mappings' and in the 'Internet Zone' for your ... Port 443 won't work because it is already used by the Default Web Site. ... What you need to do is create a wildcard certificate and use it in ISA. ... The steps to publish WSS 3.0 applications behind ISA 2004 are the same ...
    (microsoft.public.windows.server.sbs)
  • Re: companyweb from RWW
    ... "Could not open connection to the host, on port 23: ... internet should tell the tale, ... Les Connor [SBS Community Member - SBS MVP] ... This site is the default web site. ...
    (microsoft.public.windows.server.sbs)
  • Re: SharePoint 3.0: problems with external access
    ... Create a new certificate for the WSS 3.0 website? ... "Go to 'Alternate Access Mappings' and in the 'Internet Zone' for your ... Port 443 won't work because it is already used by the Default Web Site. ... What you need to do is create a wildcard certificate and use it in ISA. ...
    (microsoft.public.windows.server.sbs)