Re: Problem Connecting to Exchange Server from Outlook

The RPC proxy does work for client systems that we set up in the home
office, but they have the advantage of connecting to the Exchange server
without having to go through any restrictive firewall rules. Once we set up
the system, the user can roam to external networks (including the remote
office) and connect without issue. It's just that initial connection that's
tripping us up.

"Diane Poremsky [MVP]" <outlookmvp@xxxxxxx> wrote in message
news:F5E47708-44D9-49EB-97A5-FB739773E0E0@xxxxxxxxxxxxxxxx
is the rpc proxy configured correctly? set up a laptop inside then try
connecting from outside and see if it works.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
dailytips-subscribe-request@xxxxxxxxxxxxxxxxxxxxx

Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:
EMO-NEWSLETTER-SUBSCRIBE-REQUEST@xxxxxxxxxxxxxxxxxxxx


"DLN" <dnadon_nospm@xxxxxxxxxxx> wrote in message
news:eUV1LPmEIHA.4400@xxxxxxxxxxxxxxxxxxxxxxx
Yep, tried that but no luck. I've also tried setting up the HTTPS
settings and then clicking the "Check name" button and that didn't help
either. I've tried resetting the TCP/IP settings as per a suggestion by
a group of people that were experiencing the same problem, but it didn't
help. The office the remote staff are in blocks most outgoing traffic by
default - they only let a few key ports through like HTTP/HTTPS, IMAP,
SMTP, etc... It wouldn't surprise me if that figures into it somehow,
but I don't know what ports it's trying to use. I do see successful
authentication requests in the Exchange server's security log, so they
are partially connected - there's just some part in the process that
isn't working.

Thanks again.

"Diane Poremsky [MVP]" <outlookmvp@xxxxxxx> wrote in message
news:66028A33-B1D1-4709-94EB-8F4BDE2B6963@xxxxxxxxxxxxxxxx
no, open rpc ports is not required. it's can be difficult to configure
rpc over http remotely. Have you tried having them use a hosts file
with the external ip pointing to the internal mail server name (as seen
in outlook when accts are set up inside the network)? This will usually
take care of it.
--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
dailytips-subscribe-request@xxxxxxxxxxxxxxxxxxxxx

Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:
EMO-NEWSLETTER-SUBSCRIBE-REQUEST@xxxxxxxxxxxxxxxxxxxx


"DLN" <dnadon_nospm@xxxxxxxxxxx> wrote in message
news:uabvNwlEIHA.5228@xxxxxxxxxxxxxxxxxxxxxxx
Hello all,

I'm having a problem with some of our staff systems running Outlook
2003 connecting to our Exchange 2007 server. When they add the server
name and their username and then click the "Check Name" button, they
receive a message that states:

The action could not be completed. The connection to the Microsoft
Exchange Server is unavailable. Outlook must be online or connected to
complete this action.

I've read several posts that discusses possible solutions to this error
and I've tried most of them with no success. The staff systems are in
a remote office and not part of the domain (I don't think that should
make a difference, but who knows). Also, for the initial connection to
the Exchange Server, do I have to have the RPC ports opened through to
the Exchange server? I know that after the clients are authenticated
we can use HTTPS, but is RPC required to establish the initial
connection?

Thanks,

DLN







.