Static IPs, Front End/Back End Exchange Server setup

Discussion in 'Windows Small Business Server' started by Brock, Jul 16, 2004.

  1. Brock

    Brock Guest

    Thanks. This is a great site. My setup almost as depicted in the link
    (the 2 NICs, static IP, ISA*, and router.)

    On the back-end, my ISP ( provides a modem/router combo with
    an ISP assigned static IP address). My backend server has an ISP assigned
    static IP address as well running Win 2003 Server firewall.

    On the front-end, I have typical Local Area Network setup with a router
    connecting SBS server and local area computers.

    I plan to run the backend server with Exchange OWA only, with the frontend
    server running full blown Exchange since my users use it for their
    mailboxes. Exchange keeps on telling me that it can't forward email to my
    ISP because the ISP doesn't recognize the IP address of the LAN server
    (behind the
    firewall). I assume the ISP will only recognize the Public assigned IP
    addresses. I was thinking that the backend server could forward the mail to
    the ISP via the front-end server.

    How do I get the LAN Exchange (running SBS, too) forward the mail through
    the front-end server?
    Brock, Jul 16, 2004
    1. Advertisements

  2. Why you don't use DNS instead? You look like you have a commercial broadband

    Having said that... I'm not sure if this problem is related or not to your
    issue, but each time someone tries to use Bellsouth as a smarthost they need
    to use the IP address instead of the FQDN of the mail server. For example,
    check this thread:
    Javier Gomez [SBS MVP], Jul 16, 2004
    1. Advertisements

  3. Brock

    Jeff L Guest


    Can you please identify why you feel you need two Exchange servers?

    I think you may have the termininology backwards. Typically, people I speak
    to refer to the frontend exchange server as the public facing exchange
    server and the backend server as the internal server. A front-end server
    does not host the Exchange information store databases. Front-end servers
    accept requests from clients and forward the requests to the appropriate
    back-end server for processing.

    I would not use DNS for mail resolution if your setup is justified based on

    So you know the exchange NG is: microsoft.public.exchange2000.general

    You can setup forwarding through your WAN connected (Frontend) exchange but
    you will have to configure the server to allow relaying from only the LAN
    connected Exchange(Backend). You would then have the backend server forward
    to the frontend.

    KB of interest:
    Front-End Server Considerations in Exchange Server 2003;en-us;822443&Product=exch2003

    How to determine if an Exchange Server is a front-end server or a back-end

    You Can Configure Either Exchange Server 2003 Standard Edition or Exchange
    Server 2003 Enterprise Edition as a Front-End Server;en-us;818476&Product=exch2003

    Jeff Loucks
    Available Technology ®
    Solutions For Professionals ®
    Jeff L, Jul 16, 2004
  4. Brock

    Brock Guest

    I hadn't released that 1 exchange server could do the job.
    How do I setup forwarding through the front end server and relaying only
    through the LAN connected backend?
    Brock, Jul 16, 2004
  5. Brock

    Jeff L Guest


    If you are using SBS it would be normal to use one and only one server.


    Jeff Loucks
    Available Technology ®
    Solutions For Professionals ®
    Jeff L, Jul 17, 2004
  6. Brock

    Brock Guest

    Yes. I'm using SBS.
    So how do I activate message forwarding and relaying? ( Original question
    was > > How do I setup forwarding through the front end server and relaying
    only through the LAN connected backend?)
    Brock, Jul 17, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.