Re: OWA SSL and Ports

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Ah2003 (hialldudes_at_hotmail.com)
Date: 03/03/04 

Date: Wed, 3 Mar 2004 14:54:18 -0500

I had port 80 and 443 opened on my PIX firewall using NAT and Access-List.
However, I kept getting

The page cannot be displayed. Cannot find server or DNS server

I tired bith http://server.mydomain.com/exchange and https. Anythinig I have
to "allow" in my CISCO PIX firewall? Anything in IIS to allow external users
accessing the OWA?

Thanks.

"Christopher Ames MSFT" <a-cames@microsoft.com> wrote in message
news:Cwy5tTUAEHA.2304@cpmsftngxa06.phx.gbl...
>
> --------------------
> | From: "Ah2003" <hialldudes@hotmail.com>
> | Subject: OWA SSL and Ports
> | Date: Wed, 3 Mar 2004 09:49:07 -0500
> | Lines: 11
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> | Message-ID: <ucFrv6SAEHA.808@TK2MSFTNGP12.phx.gbl>
> | Newsgroups: microsoft.public.windows.server.sbs
> | NNTP-Posting-Host: 208.37.119.72.ptr.us.xo.net 208.37.119.72
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.sbs:47314
> | X-Tomcat-NG: microsoft.public.windows.server.sbs
> |
> | I found that by default OWA on SBS 2003 server enable SSL already.
Anyway
> to
> | disable that as the company is not willing to spend the money to get
> | ceritificate from authorties.
> |
> | We need to allow company employees to access the OWA from the Internet.
> What
> | ports needed to be opened on the firewall? 443 (SSL)? 80? I also read
> about
> | Webdav which requires some changes in the firewall settings?
> |
> | Thanks.
> |
> |
> |
> There is no need to obtain a trusted cert. The ICW will create and non
> trusted cert that will work for you. You will need 80 and 443 open for it
> to work.
>
> Thank you,
> --------------------------
> Christopher Ames
> Microsoft Online Support Engineer
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader
> so that others may learn and benefit from your issue.
>
> For SBS 4.5 issues, post to: microsoft.public.backoffice.smallbiz
> For SBS 2000 issues, post to: microsoft.public.backoffice.smallbiz2000
> For SBS 2003 issues, post to: microsoft.public.windows.server.sbs
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> </BODY>
>

Relevant Pages

  • Re: OWA through ISA Server
    ... understood I have port 75 opened in DSL router (as port 80 is blocked ... is being forwarded to external nic of ISA server since "mail server ... to port 80 on Exchange server (ISA server & Exchange are on different ... If I try OWA on ISA using http://externalipisa:75/exchange it ...
    (microsoft.public.isa)
  • Re: OWA From the Internet
    ... Did you run the CEICW wizard and enable OWA? ... If you have 2 nics in your server, ... forward port 443 from your router to your external nic IP. ... > public interface in NAT. ...
    (microsoft.public.windows.server.sbs)
  • ISA 2004 SP1 and Exchange 2003 OWA Problems
    ... I have Windows 2003 Server as a domain controller with Exchange ... An ADSL router forwards all external, inbound port 80 traffic to my ... The ISA listener is on port 81. ... >>From an external address OWA works almost perfectly. ...
    (microsoft.public.isa)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... Port 80 IS NOT NEEDED. ... Something else is still wrong with your server. ... I just remembered that I somehow hosed OWA about four years ago, ... that port 443 and port 80 must be open to use RPC over HTTP. ...
    (microsoft.public.windows.server.sbs)
  • RE: Opening up SSL port to allow OWA use
    ... can I assume that you have ISA Server installed on the SBS box? ... the external users will only be able to reach the OWA using the FQDN ... port 443 will be as safe as you can expect to be. ...
    (microsoft.public.windows.server.sbs)