Microsoft Exchange 2007 Outlook Anywhere doesn't work

I setup Outlook anywhwere on my Exchange 2007 SP1 server and it doesn't seem
to be working.  I have all the Exchange roles on one server.  

I installed the RPC over HTTP component and I have ports 80 and 443 open
thru the firewall.  I have verified that those ports are open as I can get to
them from a command line.

Outlook Web access works just fine.   The error message I get is this:

"Outlook cannot logon.  verify you are connected to the network and are
using the proper server and mailbox name.  the connection to Microsoft
Exchange is unavailable.  Outlook must be online or connected to complete
this action.  "

I followed this article to setup the Outlook Client:
http://office.microsoft.com/en-us/outlook/HP101024441033.aspx 

I verifed that NTLM is used for both the server and the client side.  

Here's the steps I took:

1.  connect via VPN and setup an Outlook profile.  Microsoft Exchange server
name MAIL2.DOMAIN.COM  
2.  follow the steps in the above article to setup Outlook Anywhere access
to use a proxy server of WEBMAIL.DOMAIN.COM
3.  disconnect from the VPN
4.  Open up Outlook

I am still getting the error message.  I even tried Basic Authentication
FlorescuAsked:
Who is Participating?
 
FlorescuConnect With a Mentor Author Commented:
I had Microsoft help me with this and we got it fixed:

After checking the registry information, I found port numbers are incorrect, please backup the registry key and refer to the following
information to change settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy]
"Enabled"=dword:00000001
"ValidPorts"="MAIL2:6001-6002;MAIL2:6004;mail2.domain.com:6001-6002;mail2.domain.com:6004"

Note: please change the domain.com to your own domain name.
0
 
NpatangCommented:
Check this article and disable the kernal Mode AUthetication if you have WIndows 2008.
http://technet.microsoft.com/en-us/library/bb123889.aspx
0
 
SaakarCommented:
Check with http://www.testexchangeconnectivity.com and verfify if Outlook Anywhere is setup properly, please paste the logs if it is not successful.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
FlorescuAuthor Commented:
Attempting to Resolve the host name webmail.domain.org in DNS.
 Host successfully Resolved
Additional Details
 IP(s) returned: 216.110.x.x

Testing TCP Port 443 on host webmail.domain.org to ensure it is listening/open.
 The port was opened successfully.

Testing SSL Certificate for validity.
 The certificate passed all validation requirements.
Test Steps
 Validating certificate name
 Successfully validated the certificate name
Additional Details
 Found hostname webmail.domain.org in Certificate Subject Common name

Validating certificate trust
 Certificate is trusted and all certificates are present in chain
Additional Details
 The Certificate chain has be validated up to a trusted root. Root = CN=Entrust.net Secure Server Certification Authority, OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS incorp. by ref. (limits liab.), O=Entrust.net, C=US

Testing certificate date to ensure validity
 Date Validation passed. The certificate is not expired.
Additional Details
 Certificate is valid: NotBefore = 7/24/2008 11:02:30 AM, NotAfter = 7/24/2009 11:30:29 AM



Testing Http Authentication Methods for URL https://webmail.domain.org/rpc/rpcproxy.dll
 Http Authentication Methods are correct
Additional Details
 Found all expected authentication methods and no disallowed methods. Methods Found: Basic, Negotiate, NTLM

Testing SSL mutual authentication with RPC Proxy server
 Successfully verified Mutual Authentication
Additional Details
 Certificate common name webmail.domain.org matches msstd:webmail.domain.org

Attempting to Ping RPC Proxy webmail.domain.org
 Pinged RPC Proxy successfully
Additional Details
 Completed with HTTP status 200 - OK

Attempting to ping RPC Endpoint 6001 (Exchange Information Store) on server mail2.domain.org
 Failed to ping Endpoint
 Tell me more about this issue and how to resolve it

Additional Details
 RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime
0
 
NpatangCommented:
Make sure sure IKE service is started
0
 
FlorescuAuthor Commented:
What IKE services?  That's for VPN.
0
 
NpatangCommented:
No thats for exchange "IKE and Auth IP sec"
0
 
SaakarCommented:
Check with this
In the host file of the Exchange server,
#::1 localhost
IPv4 address_of_Exchange_computer Host_name_of_the_Exchange_computer
IPv4 address_of_Exchange_computer FQDN_of_the_Exchange_computer

In the Exchange Server and GC we made the following registry settings:
HKLM\System\CurrentControlSet\Services\TCPIP6\Parameters
Type : DWORD
Name : DisabledComponents
Value : 0xFF
0
 
SaakarCommented:
Glad that you fixed it, well Valid Ports entries should have been checked initially
The error that you were getting in Test Exchange Connectivity were misleading, anyways
Good Luck
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.