Solved

Cannot connect outlook client

Posted on 2014-04-19
10
132 Views
Last Modified: 2014-12-04
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.
0
Comment
Question by:SSECit
10 Comments
 

Expert Comment

by:fabiod89
Comment Utility
Did you ensure that the outlook environment is connected to the same domain as the exchange?
0
 

Author Comment

by:SSECit
Comment Utility
yes, the machines are physically on our network.
0
 
LVL 24

Expert Comment

by:Mohammed Khawaja
Comment Utility
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?
0
 
LVL 12

Expert Comment

by:Vaseem Mohammed
Comment Utility
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?
0
 

Author Comment

by:SSECit
Comment Utility
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.
0
Too many email signature updates to deal with?

Do you feel like you are taking up all of your time constantly visiting users’ desks to make changes to email signatures? Wish you could manage all signatures from one central location, easily design them and deploy them quickly to users? Well, there is an easy way!

 

Author Comment

by:SSECit
Comment Utility
I have 6 servers playing various roles
0
 
LVL 9

Expert Comment

by:VirastaR
Comment Utility
Hi,

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 :)
0
 

Author Comment

by:SSECit
Comment Utility
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.
0
 
LVL 9

Expert Comment

by:VirastaR
Comment Utility
Hi,

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 :)
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
Comment Utility
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.

Simon.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now