SBS 2008 and Exchange 2007 Setting Question

Discussion in 'Windows Small Business Server' started by Ken Sheppard, Dec 17, 2008.

  1. Ken Sheppard

    Ken Sheppard Guest

    I've just deployed a new SBS 2008 server. This server is located in a
    sattelite office with about 5 PCs and users. I also have another SBS 2003
    server running at the main office, where all of the company email is
    delivered to via MX records. The SBS 2008 server POPs the email from the
    main office and delivers it to the Exchange 2007 mailboxes for the 5 users.
    This all works fine. And the two servers don't touch each other as I know
    that you cannot have 2 SBS boxes on the same network.

    Anyway, the problem that I'm having is that when a user at the remote site
    sends email to someone with the same email domain, they get an NDR because
    it cannot locate that email account on the local Exchange 2007 store. In
    Exchange 2003 there was a way to tell smtp to look for or forward same
    domain name email to another server, but I cannot locate this setting in
    Exchange 2007. Any suggestions would be appreciated.

    Ken
     
    Ken Sheppard, Dec 17, 2008
    #1
    1. Advertisements

  2. SuperGumby [SBS MVP], Dec 17, 2008
    #2
    1. Advertisements

  3. This is why SBS is not a good choice for remote offices.
     
    Cris Hanna [SBS MVP], Dec 17, 2008
    #3
  4. Hi Ken -

    Just for curiosity sake, can I ask why the two offices aren't connected? In
    this type of remote office scenario, I usually set up a router-based VPN
    between the two sites, and put a vanilla Windows Server at the remote office
    configured as an additional domain controller / global catalog for the
    domain. Users at the remote office then just connect to Exchange at the
    main office for email, and can use companyweb at the main office as well.
    The Windows Server at the remote office serves as a file server for the
    remote users' files & redirected profile folders. This also allows users at
    each office to easily access resources (such as shared printers) at each
    office.
     
    Chad A. Gross, Dec 17, 2008
    #4
  5. Ken Sheppard

    Ken Sheppard Guest

    Thanks for all of the suggestions.

    I do agree about not using SBS for remote offices and I typically do use a
    VPN scenario as Chad suggests. However, this client has an unusual need for
    a rapid remote disaster recovery location. By having the remote SBS
    location, all I need to do to get them working correctly at the new location
    is restore their SQL database for their web-based property management
    application, modify the external DNS and MX record and their working just
    fine. We got hit EXTREMELY bad last spring by the tornado that went through
    downtown Atlanta and the client simply forced me to layout a rapid disaster
    deployment plan that addresses all of the things we faced during and after
    the storm. We didn't have power or Internet at the storm location for about
    a week, which killed their business. This remote office is about 30 miles
    away and large enough to handle their staff for a small period. Sometime
    clients ask for strange things, I guess.

    I'll read the MSExchange article and see what I can find.

    Ken
     
    Ken Sheppard, Dec 17, 2008
    #5
    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.