RPC/HTTPS remote configuration

[JoJo Almario]

We are using OUtlook 2003 to connect to an Exchange 2003
server through RPC over HTTPS. We can set up and
configure it from within the LAN and once we take a
laptop outside of the LAN it will connect back to the
Exchange server fine.

However we cannot take a laptop and have it setup and
configured remotely. We followed the protocol outlined
in this article
http://www.outlookexchange.com/articles/HenrikWalther/RPC_
over_HTTP.asp .

When we get to the point that you click more settings, it
gives an error message that the Exchange server cannot be
contacted. How is this possible when we can configure
the client inside the lan and still have it connect one
we are out side?

Our Exchange server FQDN resolves out fine so I don't
think it is a dns issue from remote. Any help would be
appreciated.

 

[neo [mvp outlook]]

I tend to kill all network connections and setup the profile for RPC/HTTP
connection. Don't forget to configure it to connect via HTTP on *FAST*
networks if staff are prone to connect across any type of ethernet/broadband
connection. This way you don't have to wait for the RPC connection to
timeout before it jumps to RPC over HTTPS.