Connection to Exchange unavailable when outside of the LAN

[OscarVogel]

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]

Set him up with RPC over HTTP?

http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

 

[Dave Nickason [SBS MVP]]

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.

 

[Dave Nickason [SBS MVP]]

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.

Set him up with RPC over HTTP?

http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

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.

 

[Gerritjan]

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

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

 

[OscarVogel]

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.

Set him up with RPC over HTTP?

http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

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]

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.

Set him up with RPC over HTTP?

http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

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]

Dave N.,

I'll try that and report back.

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.

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.

 

[Brian Tillman]

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.

 

[OscarVogel]

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?

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.

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 Nickason [SBS MVP]]

Try installing the certificate again, except when you do it, manually choose
the "Trusted Root Certification Authority" instead of the default. That's
the only other thing I can think of, as long as you're setting up the
connection from outside the LAN. I've had instances where I've configured
it and had it working on the LAN, but had to do the certificate install
again from outside to get it to connect properly.

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?

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.

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]

Thanks for responding but I actually did manually choose the "Trusted Root
Certification Authority" store instead of the default.

I'm wondering if the problem may be DNS related especially since;

I see "The name on the security certificate is invalid or does not match the
name of the site." which still appears as a security alert when I us IE to
connect to RWW.

And also the fact that I am NOT able to connect to
https://remote.[company].com/remote (as specified in the RWW's
instructions). Although I AM able to connect to
"WWW.remote.[company].com/remote.

Tomorrow morning I will try to fix that "invalid or does not match the name"
problem, which I know shouldn't be happening anyway, and see if that happens
to fix it.

I'd appreciate any suggestions at all at least regarding steps to find the
source of the problem.

Thanks



might have something to do with

Try installing the certificate again, except when you do it, manually
choose the "Trusted Root Certification Authority" instead of the default.
That's the only other thing I can think of, as long as you're setting up
the connection from outside the LAN. I've had instances where I've
configured it and had it working on the LAN, but had to do the certificate
install again from outside to get it to connect properly.

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?

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.



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 Nickason [SBS MVP]]

That sounds like an issue with the external DNS, so hopefully if you get
that "does not match" thing sorted out you'll be good to go.

You can try Start -> Run -> Outlook.exe /rpcdiag, which will bring up a box
telling you what's going on with the RPC connection. I've never gotten any
useful information from it, but my problems have been certificate-based.
Yours sounds like networking, so maybe you'll have better luck.

I'm going to be away with no web access until Tuesday, so hopefully someone
else can post some suggestions if you don't get it working in the morning.

Thanks for responding but I actually did manually choose the "Trusted Root
Certification Authority" store instead of the default.

I'm wondering if the problem may be DNS related especially since;

I see "The name on the security certificate is invalid or does not match
the name of the site." which still appears as a security alert when I us
IE to connect to RWW.

And also the fact that I am NOT able to connect to
https://remote.[company].com/remote (as specified in the RWW's
instructions). Although I AM able to connect to
"WWW.remote.[company].com/remote.

Tomorrow morning I will try to fix that "invalid or does not match the
name" problem, which I know shouldn't be happening anyway, and see if that
happens to fix it.

I'd appreciate any suggestions at all at least regarding steps to find the
source of the problem.

Thanks



might have something to do with

Try installing the certificate again, except when you do it, manually
choose the "Trusted Root Certification Authority" instead of the default.
That's the only other thing I can think of, as long as you're setting up
the connection from outside the LAN. I've had instances where I've
configured it and had it working on the LAN, but had to do the
certificate install again from outside to get it to connect properly.

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?



message 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.



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]

Thanks for the help. As it turns out, the problem was with the security
certificate. I had to fix the problem with "The name on the security
certificate's invalid or does not match the name of the site."

What fixed it was creating a new certificate with an address that matched
the addressed used by Outlook to access the server.
(www.remote.[company].com). (Before the address on the certificate was the
LOCAL name of the server.) That got rid of the Security alert on the client,
and RPC over HTTP now works fine.

Thanks.

 

[Les Connor [SBS MVP]]

Unless I missed something, this error is because the URL you enter to
access the server doesn't match the certificate name.

If you reach the server at https://blah.blah.blah/remote, then the name used
for the certificate when generated in CEICW must be *exactly*
blah.blah.blah.


--
Les Connor [SBS MVP]

That sounds like an issue with the external DNS, so hopefully if you get
that "does not match" thing sorted out you'll be good to go.

You can try Start -> Run -> Outlook.exe /rpcdiag, which will bring up a
box telling you what's going on with the RPC connection. I've never
gotten any useful information from it, but my problems have been
certificate-based. Yours sounds like networking, so maybe you'll have
better luck.

I'm going to be away with no web access until Tuesday, so hopefully
someone else can post some suggestions if you don't get it working in the
morning.

Thanks for responding but I actually did manually choose the "Trusted
Root Certification Authority" store instead of the default.

I'm wondering if the problem may be DNS related especially since;

I see "The name on the security certificate is invalid or does not match
the name of the site." which still appears as a security alert when I us
IE to connect to RWW.

And also the fact that I am NOT able to connect to
https://remote.[company].com/remote (as specified in the RWW's
instructions). Although I AM able to connect to
"WWW.remote.[company].com/remote.

Tomorrow morning I will try to fix that "invalid or does not match the
name" problem, which I know shouldn't be happening anyway, and see if
that happens to fix it.

I'd appreciate any suggestions at all at least regarding steps to find
the source of the problem.

Thanks



might have something to do with

Try installing the certificate again, except when you do it, manually
choose the "Trusted Root Certification Authority" instead of the
default. That's the only other thing I can think of, as long as you're
setting up the connection from outside the LAN. I've had instances
where I've configured it and had it working on the LAN, but had to do
the certificate install again from outside to get it to connect
properly.


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?



message 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.



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.

 

[NAJJAR]

DEAR ALL
I HAVE THE SAME PROBLEM WITH SBS . I DON'T KNOW WHERE IS THE PROBLEM EXACTLY
FROM .

AT FIRST I COULDN'T CREATE USER USING THE SBS BUT I WAS ABLE TO CREATE
THEM USING ACTIVE DIRECTORY USER AND COMPUTER . AFTER THAT I START TO GET
PROBLEM IN MICROSOFT OUTLOOK IN SOME COMPUTER . SOME OF THEM ARE GETTING
DISCONNECT MESSAGE 0X8004011D BUT IT DOES CONNECT AFTER A WHILE .AND SOME
THEM DOESN'T HAVE THIS PROBLEM AT ALL .
CAN HELP
1.IS IT LICENSE PROBLEM IF IT'S OVER THE LICENSE LIMIT .
2.VIRUSES

I DON'T KNOW CAN ANYBODY HELP .

 

[Holz]

I DON'T KNOW CAN ANYBODY HELP

Google 0X8004011D