Re: OWA Setup - HELP PLS

From: Leif Pedersen [MVP] (leif.pedersenNOSPAM_at_get2net.dk)
Date: 03/07/04

  • Next message: Ward Flowers [MSFT]: "Re: New installation and ADC connector has "mis-associated" mailboxes"
    Date: Sun, 7 Mar 2004 17:08:39 +0100
    
    

    Hi,

    Best thing for you would be to use SSL - then you have to open port 443. If
    you are not conserned about security you could open port 80 instead

    Leif

    "duke2555" <anonymous@discussions.microsoft.com> skrev i en meddelelse
    news:6a5c01c4015c$9f7c9ee0$a101280a@phx.gbl...
    > the articles that you mention are great...except I am
    > running Exchange Server 2000...all of these articles
    > relate to Excgange 5.5 and lower. Do they apply to
    > Exchange 2000 as well??
    >
    > Also, one of the registry keys is
    >
    > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExch
    > angeDS\Parameters
    >
    > I don't have the "exact" registry key...I have
    >
    > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExch
    > angeDSAccess with no Parameters subkey.
    >
    >
    >
    > >-----Original Message-----
    > >XWEB: How to Configure OWA to Connect to Exchange Through
    > >a Firewall
    > >View products that this article applies to.
    > >This article was previously published under Q259240
    > >IMPORTANT: This article contains information about
    > >modifying the registry. Before you modify the registry,
    > >make sure to back it up and make sure that you understand
    > >how to restore the registry if a problem occurs. For
    > >information about how to back up, restore, and edit the
    > >registry, click the following article number to view the
    > >article in the Microsoft Knowledge Base:
    > >256986 Description of the Microsoft Windows Registry
    > >
    > >SUMMARY
    > >This article describes how to set up Microsoft Outlook
    > Web
    > >Access (OWA) to connect to Microsoft Exchange Server
    > >through a firewall. This configuration assumes that there
    > >is a firewall between OWA and the Exchange Server
    > >computer. There are three ports that need to be opened on
    > >the firewall in this configuration. On the Exchange
    > Server
    > >computer, two ports need to be statically mapped. To do
    > >this, the ports must be opened by editing the registry.
    > >
    > >NOTE: The third port, port 135, must be opened on the
    > >firewall.
    > >MORE INFORMATION
    > >Follow the steps in this section to statically map the
    > two
    > >ports on the Exchange Server computer. The Exchange
    > Server
    > >computer that OWA points to must have these ports mapped.
    > >
    > >NOTE: One port must be mapped for the information store,
    > >and one port must be mapped for the directory.
    > >
    > >For additional information about configuring Exchange
    > >Server services for Internet firewalls, click the article
    > >number below to view the article in the Microsoft
    > >Knowledge Base:
    > >155831 XADM: Setting TCP/IP for Exchange and Outlook
    > >Client Connects Through a Firewall
    > >
    > >WARNING: If you use Registry Editor incorrectly, you may
    > >cause serious problems that may require you to reinstall
    > >your operating system. Microsoft cannot guarantee that
    > you
    > >can solve problems that result from using Registry Editor
    > >incorrectly. Use Registry Editor at your own risk.
    > >
    > >
    > >Start Registry Editor (Regedt32.exe).
    > >Locate the following key in the registry:
    > >HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExc
    > h
    > >angeDS\Parameters
    > >
    > >Add the following entry for the Microsoft Exchange
    > >Directory service:
    > >Entry: TCP/IP port
    > >Type: REG_DWORD
    > >Data: port number to assign
    > >
    > >NOTE: Do not assign ports immediately above the 1023
    > >range. This may cause other problems on the Exchange
    > >Server.
    > >
    > >For example:
    > >"TCP/IP Port"=dword:000004C9(1225)
    > >
    > >Locate the following key in the registry:
    > >HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExc
    > h
    > >angeIS\ParametersSystem
    > >
    > >Add the following entry for the Exchange Server
    > >information store:
    > >Entry: TCP/IP port
    > >Type: REG_DWORD
    > >Data: port number to assign
    > >
    > >NOTE: Do not assign ports immediately above the 1023
    > >range. This may cause other problems on the Exchange
    > >Server computer.
    > >
    > >For example:
    > >"TCP/IP Port"=dword:000004CA(1226)
    > >
    > >Quit Registry Editor.
    > >Restart your computer for the changes to take effect.
    > >On the firewall, open the ports that you assigned to the
    > >directory, the information store, and port 135 for the
    > >endpoint mapper.
    > >
    > >NOTE: For the Exchange Server to communicate back through
    > >the firewall to the OWA server it is also necessary to
    > >have the ephemeral ports 1024 through 65535 configured
    > for
    > >outbound communications from the Exchange server to the
    > >OWA server. Although you can specify what ports Exchange
    > >listens on for RPC traffic, you can not specify what RPC
    > >ports the OWA application uses for RPC communications.
    > >NOTE: The OWA server must also be a member of the domain
    > >where the mailboxes reside. For additional information
    > >about how to configure that access, click the article
    > >number below to view the article in the Microsoft
    > >Knowledge Base:
    > >179442 How to Configure a Firewall for Domains and Trusts
    > >
    > >Hope it helps
    > >
    > >Sonny
    > >
    > >>-----Original Message-----
    > >>I am trying to setup OWA on my Exchange Server. I am NOT
    > >>running a front-end back-end type scenario, I only have
    > a
    > >>single Exchange 2000 Server and it is behind a CISCO
    > >>Router/Firewall. I can get an OWA logon from an Internet
    > >>Explorer page internally and get into a user's mailbox,
    > >>but when I try to type http://server.domain/exchange
    > from
    > >>home or an outside address, I get "Page cannot be found".
    > >>Do I have to open up more ports in my firewall?? I am
    > >>allowing SMTP, POP3 traffic through because we send and
    > >>receive emails to outside sources fine.
    > >>
    > >>any suggestions would be appreciated.
    > >>
    > >>.
    > >>
    > >.
    > >


  • Next message: Ward Flowers [MSFT]: "Re: New installation and ADC connector has "mis-associated" mailboxes"

    Relevant Pages

    • RE: Event ID: 2501
      ... Can you add the following Registry key. ... Create a key for SiteName and provide the proper site name. ... an Exchange only server the is in the Default-First-Site. ...
      (microsoft.public.exchange.admin)
    • RE: Event ID: 2501
      ... The nltest response seems stable now. ... Can you add the following Registry key. ... an Exchange only server the is in the Default-First-Site. ...
      (microsoft.public.exchange.admin)
    • RE: Event ID: 2501
      ... Can you add the following Registry key. ... Also check NIC binding order whether the one with DNS is at the top. ... an Exchange only server the is in the Default-First-Site. ...
      (microsoft.public.exchange.admin)
    • Re: What ports to open on firewall?
      ... Internet to Marshall and Exchange should talk with DNS server that it uses. ... Internet should be opened, if DNS Server is external, then DNS ports to DNS ...
      (microsoft.public.exchange.admin)
    • Re: What ports to open on firewall?
      ... In my LAN-->WAN, all outgoing ports are open, my exchange server is in my LAN which we use internal DNS servers. ... My issue is when I NAT, I need to know what ports to I need to NAT so the receippient server can reverse lookup, validate sender... ...
      (microsoft.public.exchange.admin)