Connecting Outlook to an Exchange account hosted overseas


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).

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

B HCommented:
can you run this test as the users:

anything useful come back there?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
samfptAuthor Commented:

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 in DNS.
  Host successfully resolved
   Additional Details
  IP(s) returned:
 Testing TCP Port 443 on host 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
Type: System.Net.Sockets.SocketException
Stack trace:
at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally()
B HCommented:
ok so they're not using secure SSL - try running the test again but tell it to not use or care about SSL
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

samfptAuthor Commented:
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
B HCommented:
hmmmmm i wonder if that's the problem.... autodiscover

as a test, can you edit the client workstation like this:
start > run > notepad.exe (run as administrator if not xp)
file > open
(hosts is the file, no extension)

at the bottom add this like:
(that's a tab after the last zero)

save it

then do start > run > cmd
ipconfig /flushdns

try your outlook again.

sometimes outlook gets real freaky with autodiscover - this effectively neuters it
samfptAuthor Commented:

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
samfptAuthor Commented:
IP also doesn't work
B HCommented:
well you could always try starting outlook as:
start > run > "outlook /rpcdiag"  (no quotes)
and see if anything useful comes out

Hi samfpt,

Is the router or firewall at the client's site set up to forward all http and https traffic to the Exchange server?
samfptAuthor Commented:
Presumbably... we can access webmail perfectly....

Try to connect with VPN. I do so for my client, who also have to work remotely to Exchange. If you can connect to Outlook inside the client's office, I think there is no need to do anything further to Outlook, just set up VPN.
samfptAuthor Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.