Re: 2 locations sharing email domain through external hosting server

Unless of course those remote clients aren't running Outlook 2003.... then I
suppose you couldn't do that.

Cheers!

Jerz


"Jerz" <Jerz@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e$rmqSa9FHA.220@xxxxxxxxxxxxxxxxxxxxxxx
> I'm just thinking out loud here but... couldn't you (or why wouldn't you)
> just add user accounts for those remote users to SBS and have exchange
> fetch their email and setup rpc over https on the remote machines so those
> users can get the mail from exchange? That way they can take advantage of
> all of the features exchange has to offer (contact sharing, calendar
> sharing, owa, etc...)
>
> Jerz
>
>
> "Mark/nwc" <Mark/nwc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:D1C57545-2782-487B-BD6B-53EB14A30FDB@xxxxxxxxxxxxxxxx
>> Recently installed new SBS2003 machine (running ISA 2004) on network and
>> ran
>> through all configuration tools. CEICW and am using POP3 Connector to
>> retrieve email from hosting company's server. Our second location has
>> just
>> three users (peer to peer) and also connects to our hosting company's
>> server
>> to send and receive email.
>>
>> Everything works great except we're not able to send email to our other
>> office through our hosting company. Our Exchange server thinks that
>> email@xxxxxxxxxxxxx belongs only on our server and doesn't send it out to
>> the
>> hosting company server. Exchange cannot find an address to deliver these
>> messages to and we get an error...
>>
>> "The following recipient(s) could not be reached:
>>
>> user@xxxxxxxxxxxxx on 11/29/2005 11:23 PM
>> The e-mail account does not exist at the organization this message was
>> sent to. Check the e-mail address, or contact the recipient directly to
>> find
>> out the correct address. <ourdomain.local #5.1.1>
>>
>> We're not hosting our own email server but I think I may have configured
>> something in Exchange with the registered FQDN and that is making it
>> difficult to send interoffice emails out to our other location. I
>> configured
>> the SMTP connector to send mail through the hosting company's IP address
>> (instead of the FQDN) but that ended up with a similar error.
>>
>> Any advice or a link in the right direction would certainly be
>> appreciated.
>> Thanks for all the great posts on all subjects. Long live technet.
>
>


.

Relevant Pages

  • Re: Errors after a clean install of SBS2K3
    ... I meant Exchange 2K3 SP1. ... > I had to reinstall SBS 2K3 because of a faulty motherboard. ... > The following settings were successfully configured by the Remote Access ... > server provided with Windows Small Business Server 2003. ...
    (microsoft.public.windows.server.sbs)
  • Exchange 2000 Connectivity Problem Through VPN
    ... I am running an Exchange 2000 Server environment with remote connectivity ...
    (microsoft.public.exchange.connectivity)
  • RE: Accessing Exchange 2000 Remotely
    ... Subject: Accessing Exchange 2000 Remotely ... web servers in the same DMZ with it. ... perhaps a better alternative would be to put your exchange server ... Our remote users have ...
    (Focus-Microsoft)
  • How do I find a local consultant for SBS -Philly area
    ... A few months ago we had sharepoint outsourced by bcentral. ... why not just buy a server and host exchange ourselves so ... We used small business server and people can login from the outside and save ... Remote access- this doesn't work because it always goes to the sharepoint ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I find a local consultant for SBS -Philly area
    ... Javier [SBS MVP] ... why not just buy a server and host exchange ourselves so ... Remote access- this doesn't work because it always goes to the ...
    (microsoft.public.windows.server.sbs)