Re: Configuring Exchange 2003 sp2 / MX records from ISP



Thank you Greg (and Steve). Yes. My ISP's default MX is 10 - I will assign
my custom one 5. Currentlly I have setup my SSL Cert as my public IP and the
users are used to it and have all added it into their personal remote
laptops/desktops. While changing it to myexternaldomain.com makes sense,
would there be a problem if I left it as the public IP? Also, I am certain
that ICW configured an appropriate rule for both OWA (port 443) and RWW (port
4125 outbound), and I havent setup sharepoint. Won't the ICW create the ISA
rule for Exchange on port 25?

Also, if I have forgotten to ask about anything, please educate me. Thanks
again for the assistance



"Gregg Hill" wrote:

Remember that the higher priority MX record is the one with a LOWER number!

You can name your server's external name anything you desire, but sticking
with "mail.myexternaldomain.com" is sensible and easy to remember. Assuming
you will be using a self-signed SSL cert created by the SBS, when you run
the CEICW to switch to Exchange and create the certificate, be sure to match
the cert name to your "mail.myexternaldomain.com" external FQDN.

A friend told me to buy a "Turbo SSL" cert at GoDaddy to make life easier
without prompts when using OWA and PDA phones.

Once you enable it all, you need port forwarding open on ports 25 for
Exchange and 443 for OWA. You may also want 444 for SharePoint and 4125 for
RDP via RWW.

You should then be able to Telnet from an EXTERNAL computer's command prompt
to your server using

telnet mail.myexternaldomain.com 25

and you should see your server's banner response.

Gregg Hill




"jdc" <jdc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:291B52C2-897D-489D-98AE-19C6B1EC24A1@xxxxxxxxxxxxxxxx
New SBS2003 R2 installation configured to use POP3 connector. Want to
modify
configuration to enable email directly to my exchange. I am prepared to
create MX record (mail.myexternaldomain.com) with a priority higher than
the
hosts default MX, and an A Record (Mail.myexternaldomain.com <-> x.x.x.x
my
external Static IP). My questions are:
Does it matter what I call my mail server in my MX record or A Record? I
run ICW and configure incoming EMAIL to use Exchange/Deliver directly to
my
server, and use my FQDN (myexternaldomain.com) for Domain. Is there any
other modifications that I need to make to complete the configuration on
my
SBS2003 server? Is there a method I can use to test the configuration
flow,
telnet?

All help appreciated, eta for changover - Sat March 17th.



.



Relevant Pages

  • Web mail blocked patch doesnt work
    ... We use Exchange 2000. ... 0.719: Setup encountered an error: Setup cannot continue because one or ... more pre-requisites required to install Hotfix for Exchange 2000 Server ...
    (microsoft.public.mac.explorer)
  • Re: Exchange 2003 SP2 - able to send but not receive email
    ... product and not part of Exchange Server itself. ... OWA already setup and running - My whole goal is to setup this server to ... settings it successfully saved my settings - ...
    (microsoft.public.exchange.admin)
  • RE: To Setup Exchange or not to Setup Exchange...That is the Question.
    ... enough rescources to handle the load that Exchange will put on it. ... into your server in no time, so you will either have to have a very fast RAID ... You can also setup RPC over HTTP for your sales people to reteive e-mail ... phones can download a simple POP client to the phone to get E-mail. ...
    (microsoft.public.exchange.setup)
  • Re: Exchange 2003 SP2 - able to send but not receive email
    ... need to be created by whomever is responsible for you external DNS Records" ... setup the mailbox's in pop3 connector right? ... product and not part of Exchange Server itself. ... OWA already setup and running - My whole goal is to setup this server to ...
    (microsoft.public.exchange.admin)
  • Re: To Setup Exchange or not to Setup Exchange...That is the Question...
    ... employees are using desktops in a corporate office, ... 2003 Standard server setup. ... Exchange connecter that we would like to be able to use (integrates ...
    (microsoft.public.exchange.setup)