Announcement

Collapse
No announcement yet.

Exchange 2003 setup without a public domain.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exchange 2003 setup without a public domain.

    Hi,
    My question is regarding a small LAN using windows server 2003 SBE and exchange server 2003 with 13 pc's joined the server domain (server. local) and the internal email working perfectly (example [email protected]l). We don't want a public domain for now, and the users have their email addresses from our isp optonline (example [email protected]). Can Exchange server be setup to send and receive email for our user's optonline.net accounts?

    In addition, how is alias setup, so if my LAN name is “bob” and my optonline email account is [email protected], so that “ bobf” should point to “bob”.

    Thanks,

  • #2
    Re: Exchange 2003 setup without a public domain.

    Exchange is really designed to have your own domain and I would strongly advise against trying to use your ISPs domain for this. Why don't you want a public domain? You can get domains for a few dollars and that is how Exchange is designed to work. It also removes the dependency on the ISP for services, so you can abandon them in the future.

    Exchange by default presumes that it is responsible for all email for a domain. Therefore if you configure it for your ISPs domain then you will have problems sending email to other users on that domain. It can be reconfigured not to behave in that way, but each time you run the wizards in SBS to change something it will be changed back.

    Use Exchange as it was designed, rather than forcing it do something else. You will find that life is much easier and the product works as it should.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Exchange 2003 setup without a public domain.

      Hi, the reason for not wanting a domain is by reason of the amount of contacts and email, we use it will take us forever to get them all to update to our new email addresses.

      Thank you very much.

      Bob

      Comment


      • #4
        Re: Exchange 2003 setup without a public domain.

        The earlier you start, the earlier you will get everyone using new information. At the moment you are at the mercy of the ISP. If the ISP decides to rebrand then you could lose those email addresses. I also don't think that ISP based email addresses look very professional.

        What I would be looking to do is get your own domain, configure Exchange to use that for all email. Then on your ISP accounts configure them to forward to your own domain. Most of your email will soon be using the new domain naturally.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Exchange 2003 setup without a public domain.

          Thanks allot we will do so.

          Bob

          Comment

          Working...
          X