[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 549
  • Last Modified:

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

0
samfpt
Asked:
samfpt
  • 6
  • 4
  • 2
  • +1
6 Solutions
 
B HCommented:
can you run this test as the users:
https://www.testexchangeconnectivity.com/

anything useful come back there?
0
 
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 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.SocketException
Stack trace:
at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally()
 
 
 
 
0
 
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
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
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
0
 
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
c:\windows\system32\drivers\etc\hosts
(hosts is the file, no extension)

at the bottom add this like:

0.0.0.0 autodiscover.greatshipglobal.com
(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
0
 
samfptAuthor Commented:
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?
0
 
raxixCommented:
Can you try with the IP address of the exchange server instead of the name
0
 
samfptAuthor Commented:
IP also doesn't work
0
 
B HCommented:
well you could always try starting outlook as:
start > run > "outlook /rpcdiag"  (no quotes)
and see if anything useful comes out

0
 
Joh_welCommented:
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?
0
 
samfptAuthor Commented:
Presumbably... we can access webmail perfectly....

0
 
Joh_welCommented:
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.
0
 
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.
0

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

  • 6
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now