• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 149
  • Last Modified:

Cannot connect outlook client

Outlook client cannot connect to exchange 2013 mailbox.  From Exchange server can telnet to port 25; cannot telnet from any other node on the network.
1 Solution
Did you ensure that the outlook environment is connected to the same domain as the exchange?
SSECitAuthor Commented:
yes, the machines are physically on our network.
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Outlook uses RPC and not SMTP if you want to use Exchange client.   If you are trying to connect over the Internet then try testing your Exchange by going to www.testexchangeconnectivity.com.  if you are teying to connect over LAN/WAN then try configuring Exchange settings by entering your fully qualified Exchange server name (ie exchangeserver.domain.local).  Also ensure to try a different computer to ensure there is nothing wrong with the PC.  Have you tried connecting via web browser to your Exchange web access?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Vaseem MohammedCommented:
Both Exchange 2013 roles are installed on same server?
If Exchange Roles (CAS, MBX) are separate, how many servers do you have?
Have you configured SSL on CAS servers?
SSECitAuthor Commented:
I can connect via webmail, but cannot connect via LAN on my network.  I have connected using the FQDN and I still won't connect.  But any webmail or mobile service will connect.  but I cannot send or receive emails through the mobile/web clients. it just goes to draft.  We were having connectivity issues before so we changed our network configuration. Now we are in a private 172.x.x.x address going to a sonicwall hosting DHCP.  the addresses are translated in the firewall to a 24.x.x.x public to the outside world.  we have set up SSL but on the web/mobile side.
SSECitAuthor Commented:
I have 6 servers playing various roles
VirastaRUC Tech Consultant Commented:

I have a couple of questions for you.

Was this working with previous version of Exchange 2007/2010?

Was this happening only after you migrated your mailboxes from previous exchange version to Exchange 2013?

Did you get a chance to check this?
Outlook 2013 profile might not update after mailbox is moved to Exchange 2013

if that doesn't help post back with answer for further assistance.

Thanks :)
SSECitAuthor Commented:
The issue began sometime last week we were getting intermittent email.  We had an issue with DNS so we moved all our public IPS to an internet host and are now using NAT on our firewall.  Our internal DNS only has the private addresses.  We can get to the internet and from the internet we can ping the mail server.  The immediate problem is from inside our network our existing outlook clients cannot send email internally or externally.  When they open outlook they go directly offline.  I created a new outlook client. I was able to resolve the name but when it tried to connect the message was that the message store was offline.
VirastaRUC Tech Consultant Commented:

Try running  EXBPA from the Exchange box

Microsoft Exchange Best Practices Analyzer v2.8

and see whether it unveils anything from exchange side.

If not,

Try running a Network trace such as Netmon or Wireshark and reproduce the problem and post if needed help with analysis.

Hope that helps :)
Simon Butler (Sembee)ConsultantCommented:
If OWA works, then HTTPS is working fine.
Outlook also uses HTTP/HTTPS to connect to Exchange 2013, RPC over TCP/IP isn't used any longer.

If you have changed your host names around, did you also update/setup a split DNS system and configure Exchange to use the correct internal host names? It sounds to me like Autodiscover is working, but then you have a DNS issue and the clients are then unable to connect.

Go through my guide here: http://semb.ee/hostnames2013 to ensure that Exchange is configured correctly.

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.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now