RE: How to setup OWA-only server?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Alan Sun [MSFT] (v-asun_at_online.microsoft.com)
Date: 04/06/04


Date: Tue, 06 Apr 2004 06:32:16 GMT

Jim,

I notice this issue is duplicated with the post in the following newsgroups:
microsoft.public.exchange2000.connectivity

I have replied you in the original thread. For your convenience, I have
included it as follows. If you have further concern, feel free to reply to
the original thread. Have a great day!

Thanks & Regards
Alan Sun
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jim,

Thanks for your posting here.

First, I would like to say it is unable to build a separate OWA server in
Exchange 2000 environment as you did in Exchange 5.5. However, there is a
similar feature Front-End.

On a Front-End server, you can configure OWA and SMTP services without
mailboxes or sensitive data. And the Front-End server can be put into the
DMZ. You need to configure the firewalls to let OWA and SMTP traffic pass
through.

To designate a front-end server, use the following instructions:
1. Install the server running Exchange in the organization.
Note: Only servers running Exchange 2000 Server Enterprise Edition can be
configured as front-end servers.
2. Use Exchange System Manager to go to the server object, right-click the
server object, and then click roperties.
3. Select This is a front-end server, and then close the page.
4. To begin using the front-end server, do one of the following:
  -- Restart the computer.
  -- Stop and restart the HTTP, POP, and IMAP services.

On the Internet firewall, following ports should be published:

         443/TCP - inbound HTTPS (SSL-secured HTTP) / 80//TCP inbound HTTP
         993/TCP - inbound SSL-secured IMAP / 143/TCP inbound IMAP
         995/TCP - inbound SSL-secured POP /110/TCP inbound POP
         25/TCP - inbound SMTP

On the Intranet firewall, these ports are needed to be published:

         80/TCP - inbound HTTP
         143/TCP - inbound IMAP
         110/TCP - inbound POP
         25/TCP - inbound SMTP
         53/TCP,UDP -Domain Name System (DNS).
         88/TCP,UDP - Kerberos authentication.
         123/UDP - Windows Time Synchronization Protocol (NTP). This is not
required for Windows 2000 logon capability, but it may be configured or
required by the network administrator.
         135/TCP - EndPointMapper.
         389/TCP, UDP - Lightweight Directory Access Protocol (LDAP).
         445/TCP - Server message block (SMB) for Netlogon, LDAP conversion and
Microsoft Distributed File System (DFS) discovery.
         3268/TCP - LDAP to global catalog servers.
         One port for the Active Directory logon and directory replication
interface (universally unique identifiers [UUIDs]
12345678-1234-abcd-ef00-01234567cffb and
e3514235-4b06-11d1-ab04-00c04fc2dcd2). This is typically assigned port 1025
or 1026 during startup. This value is not set in the DSProxy or System
attendant (MAD) source code. Therefore, you must map the port in the
registry on any domain controllers that the Exchange 2000 computer must
contact through the firewall to process logons, and then open the port on
the firewall.

To map the port in the registry:
a. Start Registry Editor (Regedt32.exe).
b. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters

c. On the Edit menu, click Add Value, and then add the following registry
value:
Value Name: TCP/IP Port
Data Type: REG_DWORD
Radix: Decimal
Value: greater than 1024

For detailed information about how to use/deploy front-end server, take a
look at the following while paper "Using Microsoft Exchange 2000 Front-End
Servers", which available at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=AFAD8426-572E-40F8-
99DA-EB7198F374C4&displaylang=en

For the more information about the ports publish on the internal firewall,
look into the following article:

280132 XCCC: Exchange 2000 Windows 2000 Connectivity Through Firewalls
http://support.microsoft.com/?id=280132

Hope this helps. Have a nice day!

Thanks & Regards
Alan Sun
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
     From: "jim" <jim@NOSPAM.com>
     Subject: How to setup OWA-only server?
     Date: Mon, 5 Apr 2004 14:34:32 -0400
     Lines: 16
     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: <e16EkyzGEHA.2308@tk2msftngp13.phx.gbl>
     Newsgroups:
microsoft.public.exchange2000.admin,microsoft.public.exchange2000.general
     NNTP-Posting-Host: pat.axcelis.com 12.146.8.100
     Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
     Xref: cpmsftngxa06.phx.gbl microsoft.public.exchange2000.general:53786
microsoft.public.exchange2000.admin:101133
     X-Tomcat-NG: microsoft.public.exchange2000.admin
     
     In our previous Ex5.5 environment, we had an OWA server in the DMZ
which was
     used to access company email by users not on the corporate network.
That
     server had only the OWA part of Exchange 5.5 installed (that is, no
     information store, directory, or site affiliation). Now we're in Ex2K
     native mode and i'm trying to recreate this configuration as before. I
     cannot see how to install just Ex2K OWA without installing the other
base
     components. In addition, when i allow it to install the base
components, it
     then wants to join an existing Admin Group, which i DON'T want it to
do. I
     just want a free-standing Ex2K OWA front end to sit out in our DMZ.
How can
     i do this? Are there TechNet articles that go over it?
     
     Thanks!
     
     *We have multiple Admin Groups/Sites within our Ex2K org..
     
     
     



Relevant Pages

  • RE: DNS and Exchange issues
    ... with the Exchange Server after you have installed the patch 888619. ... XFOR: Telnet to Port 25 of IMC to Test IMC Communication: ... Start Exchange System Manager. ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, ...
    (microsoft.public.exchange.setup)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 - POP3 only delivers email to Administrator
    ... Server to allow internet users access Exchange through POP3 services, ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.setup)