ascendmax26
asked on
Trouble connecting Outlook 2010 with Exchange 2010 server
I am trying to configure my Outlook 2010 client to connect to a newly installed Exchange 2010 server. I keep getting the following error message:
"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."
My connection settings are as follows:
URL https://myserver.com
Only connect to proxy servers.... msstd:myserver.com
On slow networks... (checked)
Basic Authentication (I have also tried NTLM)
Nothing seems to work. I have tried this on multiple devices, all running Outlook 2010, and trying to connect to multiple mailboxes. OWA works fine.
What am I doing wrong?
"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."
My connection settings are as follows:
URL https://myserver.com
Only connect to proxy servers.... msstd:myserver.com
On slow networks... (checked)
Basic Authentication (I have also tried NTLM)
Nothing seems to work. I have tried this on multiple devices, all running Outlook 2010, and trying to connect to multiple mailboxes. OWA works fine.
What am I doing wrong?
ASKER
I am able to connect while I am on the office LAN without using the Outlook Anywhere settings. Still no luck outside the network though.
Where can I check the CAS array setting?
DNS is resolving correctly on the client. Are you referring to my default gateway in my network settings? If so, I have the proper gateway configured as well.
Thanks
Where can I check the CAS array setting?
DNS is resolving correctly on the client. Are you referring to my default gateway in my network settings? If so, I have the proper gateway configured as well.
Thanks
Onething which I observed is that you mentioned URL as https://servername.com, whereas, it should be https://servername.domain.com usually people use https://mail.domain.com
The name entry against mail.domain.com should exist on internal DNS pointing to your CAS Server. This should also be published on the external DNS and Outlook Anywhere publishing rule should also exist on the Firewall.
Set the Outlook Anywhere Directory on all the CAS Servers using Exchange Management Shell with the following commands,
Enable-OutlookAnywhere –Server 'Servername' –ExternalHostname “mail.domain.com” –DefaultAuthenticationMeth od “Basic” –SSLOffloading $false
Set-OutlookProvider EXPR –CertPrincipalName msstd:mail.domain.com
You should also have a SAN Certificate which is configured on the CAS servers. Either a local CA be used or purchased certificate from a reknowned Global Certificate authority be used.
If you used a local SAN certificate then the root certificate should be installed on the client computer before accessing the Exchange server from outside.
For detail configuration, I am also sending an article
http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html
The name entry against mail.domain.com should exist on internal DNS pointing to your CAS Server. This should also be published on the external DNS and Outlook Anywhere publishing rule should also exist on the Firewall.
Set the Outlook Anywhere Directory on all the CAS Servers using Exchange Management Shell with the following commands,
Enable-OutlookAnywhere –Server 'Servername' –ExternalHostname “mail.domain.com” –DefaultAuthenticationMeth
Set-OutlookProvider EXPR –CertPrincipalName msstd:mail.domain.com
You should also have a SAN Certificate which is configured on the CAS servers. Either a local CA be used or purchased certificate from a reknowned Global Certificate authority be used.
If you used a local SAN certificate then the root certificate should be installed on the client computer before accessing the Exchange server from outside.
For detail configuration, I am also sending an article
http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html
ASKER
The url is https://mail.domain.com.
DNS is configured internally and externally and the firewall is configured.
The shell commands were already set.
I have a GoDaddy CA that is installed.
When I run a test on www.testexchangeconnectivity.com I fail with the following error:
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server mail.domain.com.
The attempt to ping the endpoint failed.
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
DNS is configured internally and externally and the firewall is configured.
The shell commands were already set.
I have a GoDaddy CA that is installed.
When I run a test on www.testexchangeconnectivity.com I fail with the following error:
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server mail.domain.com.
The attempt to ping the endpoint failed.
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for ascendmax26's comment #37690757
for the following reason:
Self solved.
Accepted answer: 0 points for ascendmax26's comment #37690757
for the following reason:
Self solved.
I think you have not followed the steps send in the link.
http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html
http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html
ASKER
You are correct. I did not follow those steps. The article was too long and confusing for me. I was able to resolve the issue anyways.
Configure the account manually and check. Also confirm have you set the CAS array setting on the database.
Also check the DNS at the Client side and Verify that the gateway should be entered in the network settings.