Re: New Exchange Server Installation

From: Todd Seagraves (nospam_todd.seagraves_at_gbe.com)
Date: 09/07/04 

Date: Tue, 07 Sep 2004 08:41:21 GMT

If your taking recommendations...
1. One NIC is fine, because you want this on your private network anyway.
2. Pseudo-direct. Put it behind a firewall and allow port 25 in to that
servers IP only.
3. Your server is going to be named by whatever you call this server
followed by your AD domain name. i.e. server.ADdomain.com. You can masq.
the FQDN if needed for outbound mail. Again, behind a firewall is ideal and
your DNS records would point to the firewall, then the firewall would
redirect traffic.
4. Yes you can host multiple domains on the server by defining which domains
this server processes mail for and recipient policies

If a firewall or some variation of that is not an option then you would
defiantly want to use 2 nic's to segment your private network from the
internet. This would allow your workstations to be on a private IP and the
server would be on both Private and Public.

You didn't say much about your current infrastructure, if any. So I don't
know if firewalls, DMZ's, or any other means of security are already
implemented. If they are, defiantly use them. Keep the server on the
private network and let the firewall do its job of protecting the network.
A couple simple ACL's would easily allow port 25 traffic to come from the
outside and only go the Exchange server, and 80/443 if you plan on
implementing OWA anytime.

Todd

"Rising" <anonymous@discussions.microsoft.com> wrote in message
news:051d01c494a8$59e82860$a401280a@phx.gbl...
> Hi,
>
> I am setting up a new Exchange Server 2003 box with a
> requiremnet for inbound and outbound Internet email
> facility. I have the Exchange 2003 standard edition
> software, domain name is reigistered, and a Public IP
> address is available. MX record will be created. Please
> suggest that whether the following are required:
>
> 1. Two Network cards are reqd or one is suffcient?
> 2. Direct Internet Connection on the server?
> 3. Should the server name be abc.xyz.com, where xyz.com is
> the registered domain name or it can be anything like
> abc.def.com (assuming def.com domain is not registered
> with ISP?.
> 4. Can I host multiple domains on one Exchange Server 2003
> box.
>
> Your help in this is very much appreciated and thanks in
> advance.
>

Relevant Pages

  • RE: FW: Exchange Server and External Access
    ... Why not vpn to your network through the linux firewall. ... Currently what i have set up is a Linux server ... connections to the exchange server. ... internet connection. ...
    (Security-Basics)
  • Re: CEICW fails at firewall config
    ... Do you or do you not have ISA 2000 or ISA 2004 installed on the SBS server? ... Do you have 2 NICs in the SBS? ... CEICW fails on firewall configuration every time. ... >>> Call to Creating the protected networks access rule returned ok. ...
    (microsoft.public.windows.server.sbs)
  • Re: Recycler security issues on IIS server
    ... > latest upates to the server. ... > like to see the server put behind our firewall, ... other software, install all patches, IISlockdown, URLscan, use the correct ... the procedures you follow may vary depending on your security needs. ...
    (microsoft.public.inetserver.iis.security)
  • Re: ISA SERVER NOT STARTING
    ... I delete the nat/basic firewall and stop and started the RRAS an tried to ... There were no critical events in the DNS Server Log in the last 24 hours. ... An error occurred during logon ... Caller User Name: - ...
    (microsoft.public.windows.server.sbs)
  • Re: For Microsoft Partners and Customers Who Cant Download or Access
    ... to reconfigure the firewall, but to use a static IP on your client ... and to make sure that the DNS server entries on the client are ... Microsoft for msdn2.microsoft.com. ... use a static IP and set the DNS server addresses to the DNS ...
    (microsoft.public.dotnet.general)
Loading