samfpt
asked on
Connecting Outlook to an Exchange account hosted overseas
Hi,
One of my clients has their main office in Malaysia and their server (including Exchange server) is managed by a local IT company. They also have a small office in another countrty, with 2 users. I am trying to setup Microsoft Outlook for these 2 users, but cannot get it to connect or lookup the names.
Note, both users are just using Local accounts, they are not a part of any domain. Not that it should matter...?
I have all of the relevant details, Exchange server name, usernames, passwords, HTTP proxy connection address etc. But I still receive the error :
"The name could not be resolved. The connection to Microsoft exchange server is unavailable. Outlook must be online or connected to complete this action"
Yet, both users can access webmail for the account just fine.
Am I missing a really obvious detail? I have setup Exchange account for many clients many times. I have had success setting up an account on both of these PC's with a local Exchange server (a different domain, just for testing purposes).
One of my clients has their main office in Malaysia and their server (including Exchange server) is managed by a local IT company. They also have a small office in another countrty, with 2 users. I am trying to setup Microsoft Outlook for these 2 users, but cannot get it to connect or lookup the names.
Note, both users are just using Local accounts, they are not a part of any domain. Not that it should matter...?
I have all of the relevant details, Exchange server name, usernames, passwords, HTTP proxy connection address etc. But I still receive the error :
"The name could not be resolved. The connection to Microsoft exchange server is unavailable. Outlook must be online or connected to complete this action"
Yet, both users can access webmail for the account just fine.
Am I missing a really obvious detail? I have setup Exchange account for many clients many times. I have had success setting up an account on both of these PC's with a local Exchange server (a different domain, just for testing purposes).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There isn't an option to specifiy not using SSL.
But to clarify, I'm selecting the option 'Outlook Anywhere (RPC over HTTP) '
and specifying the server option manually.
Using the Autodiscover option also failed
But to clarify, I'm selecting the option 'Outlook Anywhere (RPC over HTTP) '
and specifying the server option manually.
Using the Autodiscover option also failed
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Bryon,
Unfortunately not. I followed those steps to the letter, but no different.
Any other thoughts?
I've had the same issue with a totally different client, Exchange server based local to me, client office in Malaysia (opposite to current issue) and have the same problem...
Surely there must be something missing here?
Unfortunately not. I followed those steps to the letter, but no different.
Any other thoughts?
I've had the same issue with a totally different client, Exchange server based local to me, client office in Malaysia (opposite to current issue) and have the same problem...
Surely there must be something missing here?
Can you try with the IP address of the exchange server instead of the name
ASKER
IP also doesn't work
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Presumbably... we can access webmail perfectly....
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
In the end it was to do with the Security Certificates, they weren't installed in the correct directory, they needed to be in the 'Trusted Root Certification Authorities" directory.
ASKER
Bryon, great testing tool thank you. Results as follows:
ExRCA is testing RPC/HTTP connectivity.
The RPC/HTTP test failed.
Test Steps
Attempting to resolve the host name mail.greatshipglobal.com in DNS.
Host successfully resolved
Additional Details
IP(s) returned: xxx.xx.xxx.xxx
Testing TCP Port 443 on host mail.greatshipglobal.com to ensure it is listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with remote host
Exception details:
Message: No connection could be made because the target machine actively refused it xxx.xx.xxx.xxx:443
Type: System.Net.Sockets.SocketE
Stack trace:
at System.Net.Sockets.TcpClie
at Microsoft.Exchange.Tools.E