I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've configured
it to use Cached Exchange Mode. The Exchange server is on a SBS 2003
Standard Edition server. Everything seems to work OK from the office. But
when I take the laptop home, I get this error message;

"The connection to the Microsoft Exchange Server is unavailable. Outlook
must be online to complete this action."

After that a dialog box appears showing the Exchange server's address (using
public IP address) and the mailbox. When I click the button to check name I
get another popup that says;

"The name could not be resolved... (then repeats the previous error
message).

Then if I first make a VPN connection to the Exchange server, everything
seems to work OK again, just like when at the office. BUT at some point the
server's address changes from the public IP address to the local DNS address
(i.e., "[server].[domain].local").

The Sales Rep would rather not make a VPN connection every time he wants to
use Outlook.

How can I get Outlook to work over the internet without using a VPN? Or is
there some other way I should be approaching this? Thanks.

Set him up with RPC over HTTP?

http://www.petri.co.il/configure_rpc...gle_server.htm

"OscarVogel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
> configured it to use Cached Exchange Mode. The Exchange server is on a
> SBS 2003 Standard Edition server. Everything seems to work OK from the
> office. But when I take the laptop home, I get this error message;
>
> "The connection to the Microsoft Exchange Server is unavailable. Outlook
> must be online to complete this action."
>
> After that a dialog box appears showing the Exchange server's address
> (using public IP address) and the mailbox. When I click the button to
> check name I get another popup that says;
>
> "The name could not be resolved... (then repeats the previous error
> message).
>
> Then if I first make a VPN connection to the Exchange server, everything
> seems to work OK again, just like when at the office. BUT at some point
> the server's address changes from the public IP address to the local DNS
> address (i.e., "[server].[domain].local").
>
> The Sales Rep would rather not make a VPN connection every time he wants
> to use Outlook.
>
> How can I get Outlook to work over the internet without using a VPN? Or
> is there some other way I should be approaching this? Thanks.
>

Connect to RWW from outside the LAN. If you don't have your firewall
configured to allow this, connect the VPN first while you're configuring
this. On the RWW main page, click "Configure Outlook via the Internet."
Print the resulting document and follow the steps exactly, which will
configure Outlook to connect using RPC over HTTPS. You will need to open
port 443 in the firewall to allow this, if it's not already.

Now, when he opens Outlook, he'll be prompted for his username and password,
but Outlook will connect seamlessly to the Exchange server, and work just as
it does when he's in the office. You may want to configure the send/receive
and other settings in Outlook for better performance when working remotely.



"OscarVogel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
> configured it to use Cached Exchange Mode. The Exchange server is on a
> SBS 2003 Standard Edition server. Everything seems to work OK from the
> office. But when I take the laptop home, I get this error message;
>
> "The connection to the Microsoft Exchange Server is unavailable. Outlook
> must be online to complete this action."
>
> After that a dialog box appears showing the Exchange server's address
> (using public IP address) and the mailbox. When I click the button to
> check name I get another popup that says;
>
> "The name could not be resolved... (then repeats the previous error
> message).
>
> Then if I first make a VPN connection to the Exchange server, everything
> seems to work OK again, just like when at the office. BUT at some point
> the server's address changes from the public IP address to the local DNS
> address (i.e., "[server].[domain].local").
>
> The Sales Rep would rather not make a VPN connection every time he wants
> to use Outlook.
>
> How can I get Outlook to work over the internet without using a VPN? Or
> is there some other way I should be approaching this? Thanks.
>

That's a great article, but please note that SBS does all the server-side
configuration for you. You don't need to do any of the steps shown for
Exchange, IIS, etc. You should just be able to do the client-side steps
from the doc on the RWW page, and let the server take care of itself.


"Betelgeuse" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Set him up with RPC over HTTP?
>
> http://www.petri.co.il/configure_rpc...gle_server.htm
>
> "OscarVogel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
>> configured it to use Cached Exchange Mode. The Exchange server is on a
>> SBS 2003 Standard Edition server. Everything seems to work OK from the
>> office. But when I take the laptop home, I get this error message;
>>
>> "The connection to the Microsoft Exchange Server is unavailable. Outlook
>> must be online to complete this action."
>>
>> After that a dialog box appears showing the Exchange server's address
>> (using public IP address) and the mailbox. When I click the button to
>> check name I get another popup that says;
>>
>> "The name could not be resolved... (then repeats the previous error
>> message).
>>
>> Then if I first make a VPN connection to the Exchange server, everything
>> seems to work OK again, just like when at the office. BUT at some point
>> the server's address changes from the public IP address to the local DNS
>> address (i.e., "[server].[domain].local").
>>
>> The Sales Rep would rather not make a VPN connection every time he wants
>> to use Outlook.
>>
>> How can I get Outlook to work over the internet without using a VPN? Or
>> is there some other way I should be approaching this? Thanks.
>>
>
>

you should use RPC over HTTP. Go to:
https://yourdomainname.com/Remote/outlook.aspx

and
http://support.microsoft.com/kb/833401/en-us




"OscarVogel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
> configured it to use Cached Exchange Mode. The Exchange server is on a
> SBS 2003 Standard Edition server. Everything seems to work OK from the
> office. But when I take the laptop home, I get this error message;
>
> "The connection to the Microsoft Exchange Server is unavailable. Outlook
> must be online to complete this action."
>
> After that a dialog box appears showing the Exchange server's address
> (using public IP address) and the mailbox. When I click the button to
> check name I get another popup that says;
>
> "The name could not be resolved... (then repeats the previous error
> message).
>
> Then if I first make a VPN connection to the Exchange server, everything
> seems to work OK again, just like when at the office. BUT at some point
> the server's address changes from the public IP address to the local DNS
> address (i.e., "[server].[domain].local").
>
> The Sales Rep would rather not make a VPN connection every time he wants
> to use Outlook.
>
> How can I get Outlook to work over the internet without using a VPN? Or
> is there some other way I should be approaching this? Thanks.
>

Thanks for the advice. I will try that. I'll follow instructions from
KB833401 (How to configure RPC over HTTP in Exchange Sever 2003).

I'll report the results. (I half remember trying RPC over HTTP in the past
but being unsuccessful. We'll see.)

Please let me know if there are better instructions, or other ideas.


"Betelgeuse" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Set him up with RPC over HTTP?
>
> http://www.petri.co.il/configure_rpc...gle_server.htm
>
> "OscarVogel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
>> configured it to use Cached Exchange Mode. The Exchange server is on a
>> SBS 2003 Standard Edition server. Everything seems to work OK from the
>> office. But when I take the laptop home, I get this error message;
>>
>> "The connection to the Microsoft Exchange Server is unavailable. Outlook
>> must be online to complete this action."
>>
>> After that a dialog box appears showing the Exchange server's address
>> (using public IP address) and the mailbox. When I click the button to
>> check name I get another popup that says;
>>
>> "The name could not be resolved... (then repeats the previous error
>> message).
>>
>> Then if I first make a VPN connection to the Exchange server, everything
>> seems to work OK again, just like when at the office. BUT at some point
>> the server's address changes from the public IP address to the local DNS
>> address (i.e., "[server].[domain].local").
>>
>> The Sales Rep would rather not make a VPN connection every time he wants
>> to use Outlook.
>>
>> How can I get Outlook to work over the internet without using a VPN? Or
>> is there some other way I should be approaching this? Thanks.
>>
>
>

Betelgeuse,

At first I didn't see your link to Petri. But I will read it. (But may
first try the RSS method described by Dave N.) Thanks.


"Betelgeuse" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Set him up with RPC over HTTP?
>
> http://www.petri.co.il/configure_rpc...gle_server.htm
>
> "OscarVogel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
>> configured it to use Cached Exchange Mode. The Exchange server is on a
>> SBS 2003 Standard Edition server. Everything seems to work OK from the
>> office. But when I take the laptop home, I get this error message;
>>
>> "The connection to the Microsoft Exchange Server is unavailable. Outlook
>> must be online to complete this action."
>>
>> After that a dialog box appears showing the Exchange server's address
>> (using public IP address) and the mailbox. When I click the button to
>> check name I get another popup that says;
>>
>> "The name could not be resolved... (then repeats the previous error
>> message).
>>
>> Then if I first make a VPN connection to the Exchange server, everything
>> seems to work OK again, just like when at the office. BUT at some point
>> the server's address changes from the public IP address to the local DNS
>> address (i.e., "[server].[domain].local").
>>
>> The Sales Rep would rather not make a VPN connection every time he wants
>> to use Outlook.
>>
>> How can I get Outlook to work over the internet without using a VPN? Or
>> is there some other way I should be approaching this? Thanks.
>>
>
>

Dave N.,

I'll try that and report back.


"Dave Nickason [SBS MVP]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Connect to RWW from outside the LAN. If you don't have your firewall
> configured to allow this, connect the VPN first while you're configuring
> this. On the RWW main page, click "Configure Outlook via the Internet."
> Print the resulting document and follow the steps exactly, which will
> configure Outlook to connect using RPC over HTTPS. You will need to open
> port 443 in the firewall to allow this, if it's not already.
>
> Now, when he opens Outlook, he'll be prompted for his username and
> password, but Outlook will connect seamlessly to the Exchange server, and
> work just as it does when he's in the office. You may want to configure
> the send/receive and other settings in Outlook for better performance when
> working remotely.
>
>
>
> "OscarVogel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
>> configured it to use Cached Exchange Mode. The Exchange server is on a
>> SBS 2003 Standard Edition server. Everything seems to work OK from the
>> office. But when I take the laptop home, I get this error message;
>>
>> "The connection to the Microsoft Exchange Server is unavailable. Outlook
>> must be online to complete this action."
>>
>> After that a dialog box appears showing the Exchange server's address
>> (using public IP address) and the mailbox. When I click the button to
>> check name I get another popup that says;
>>
>> "The name could not be resolved... (then repeats the previous error
>> message).
>>
>> Then if I first make a VPN connection to the Exchange server, everything
>> seems to work OK again, just like when at the office. BUT at some point
>> the server's address changes from the public IP address to the local DNS
>> address (i.e., "[server].[domain].local").
>>
>> The Sales Rep would rather not make a VPN connection every time he wants
>> to use Outlook.
>>
>> How can I get Outlook to work over the internet without using a VPN? Or
>> is there some other way I should be approaching this? Thanks.
>>
>
>

OscarVogel <(E-Mail Removed)> wrote:

> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
> configured it to use Cached Exchange Mode. The Exchange server is on
> a SBS 2003 Standard Edition server. Everything seems to work OK from
> the office. But when I take the laptop home, I get this error
> message;
> "The connection to the Microsoft Exchange Server is unavailable.
> Outlook must be online to complete this action."

He should be using Outlook in Offline mode in order to use Outlook while
away from the office as though he were connected. Usually, you set the mail
profile to automatically detect whether to check if connected or not or to
ask whether or not to work in Offline mode.
--
Brian Tillman [MVP-Outlook]

That did NOT work (unless I VPN). I was very careful to follow the RWW's
instructions for configuring RPC over HTTP. But after doing so;

-When I open Outlook, at first "Trying to connect..." shows in the lower
right hand corner for approximately 30 seconds, then it changes to
"disconnected". When I try to Send/Receive, I get these 2 errors.
---Task 'Microsoft Exchange Server' reported error (0x8004011D): the server
is not available...
---Task 'Microsoft Exchange Server - Sending' reported error (0x80040115):
The connection to the is unavailable. Outlook must be online or connected to
complete this action.

IS IT POSSIBLE THAT ANY OF THESE ISSUES COULD BE CAUSING THE PROBLEM?

-When I tried to "Verify that the computer trusts the certificate used by
the server", I was NOT able to connect using https://remote.[company's
domain name]/remote. ("The page cannot be displayed. The page you are
looking for is currently unavailable..." But I WAS able to at least connect
using www.remote.[company's domain name]/remote.

-When I used IE to connect to "www.remote.[company's domain name]/remote", I
installed the certificate in the "Trusted root certificate" store. That took
care of the "cert not trusted" message, but it STILL shows "The name on the
security certificate is invalid or does not match the name of the site."
(Although I am able to click on "proceed" to access the site.)

-And to log on to the RWW site, "[Windows Domain Name]\[User Name]" does NOT
work, but [User Name] (w/out domain) DOES work.

I'm guessing that I have something configured wrong on the server. Let me
know if I can provide any additional info. Can any of you give me any
advice on what could be stopping both RPC over HTTP from working?



"Dave Nickason [SBS MVP]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Connect to RWW from outside the LAN. If you don't have your firewall
> configured to allow this, connect the VPN first while you're configuring
> this. On the RWW main page, click "Configure Outlook via the Internet."
> Print the resulting document and follow the steps exactly, which will
> configure Outlook to connect using RPC over HTTPS. You will need to open
> port 443 in the firewall to allow this, if it's not already.
>
> Now, when he opens Outlook, he'll be prompted for his username and
> password, but Outlook will connect seamlessly to the Exchange server, and
> work just as it does when he's in the office. You may want to configure
> the send/receive and other settings in Outlook for better performance when
> working remotely.
>
>
>
> "OscarVogel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm trying to set up Outlook 2003 on a Sales Rep's laptop. I've
>> configured it to use Cached Exchange Mode. The Exchange server is on a
>> SBS 2003 Standard Edition server. Everything seems to work OK from the
>> office. But when I take the laptop home, I get this error message;
>>
>> "The connection to the Microsoft Exchange Server is unavailable. Outlook
>> must be online to complete this action."
>>
>> After that a dialog box appears showing the Exchange server's address
>> (using public IP address) and the mailbox. When I click the button to
>> check name I get another popup that says;
>>
>> "The name could not be resolved... (then repeats the previous error
>> message).
>>
>> Then if I first make a VPN connection to the Exchange server, everything
>> seems to work OK again, just like when at the office. BUT at some point
>> the server's address changes from the public IP address to the local DNS
>> address (i.e., "[server].[domain].local").
>>
>> The Sales Rep would rather not make a VPN connection every time he wants
>> to use Outlook.
>>
>> How can I get Outlook to work over the internet without using a VPN? Or
>> is there some other way I should be approaching this? Thanks.
>>
>
>