Solved

Outlook 2016 doesn't update to new server IP address

Posted on 2016-09-19
9
92 Views
Last Modified: 2016-10-18
The public IP address of the Exchange server has changed.
I have updated the Autodiscover DNS record and have waited couple of days for the DNS change to propagate.

After the change, at least one Outlook 2016 client can't connect.  It keeps asking for password and it looks like it has not updated the IP address.

How can I force it to update the IP address?  When I go to 'accounts-> change -> more settings' there are no visible fields for servers' address.
0
Comment
Question by:ivolach
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 2
9 Comments
 
LVL 30

Expert Comment

by:Scott C
ID: 41804694
Try the MS Outlook connectivity tester and make sure AutoDiscover is working correctly.

https://testconnectivity.microsoft.com/

Also, you have SBS tagged...what version of SBS are we looking at here?

If it's SBS 2007, then Outlook 2016 isn't a supported client for that version of Exchange.  SBS 2010 should be fine.
0
 

Author Comment

by:ivolach
ID: 41804718
It is SBS2011 hence, Exchange 2010.

The connectivity test is successful, and I have another Outlook 2016 client that has been updated successfully.
The get the successful one working, I had to start/stop few times until a message came up asking if I want to allow the autodiscover to make necessary changes.

Thanks,
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 41805060
Outlook doesn't maintain a list of server IP addresses. It does a DNS lookup.
Therefore forget it is Outlook for a moment. From the machine that doesn't work you should be able to browse to the Outlook Anywhere address - usually https://remote.example.com with SBS 2011 and see the RWW.

If that doesn't work, then the issue is unrelated to Outlook. You then need to do standard troubleshooting for DNS resolution failure. PING and NSLOOKUP to the host name to see if they resolve correctly.

Being picky, there is no such thing as DNS propagation time. The only thing that ever has to propagate is name server changes. DNS changes take time to go live because DNS is cached around the world and that cache has to expire. That is usually 48 hours at most. If you are still seeing old results then it could be that a cache has got stuck, or the workstation has a hosts file on it which is overriding.
0
Free Webinar: AWS Backup & DR

Join our upcoming webinar with experts from AWS, CloudBerry Lab, and the Town of Edgartown IT to discuss best practices for simplifying online backup management and cutting costs.

 

Author Comment

by:ivolach
ID: 41808666
Thanks,
I am waiting for the user to follow the suggestions
0
 

Author Comment

by:ivolach
ID: 41812412
Following testing:
- the connectivity test comes back OK
- Ping and nslookup return different results: the ping returns the right result, the nslookup returns the internal IP for the server rather than the public IP for the remote access.

I have checked the hosts file and there is nothing there.  Tried to add an entry for the public domain with no change in results.  run ipconfig /flushdns, still no change.
0
 

Author Comment

by:ivolach
ID: 41812462
Following a modem reset, nslookup and ping are now resolving to the right IP address.
However, Outlook keeps asking for password, and is not connecting.
0
 

Author Comment

by:ivolach
ID: 41813859
I have tested with 'outlook.exe /rpcdiag' and it looks like outlook is trying to connect to the internal 'server.local' rather than the public 'mail.server.com'
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 41814666
That is the expected behaviour.
Outlook will initially try to connect to the server's real name, then failover to the Outlook Anywhere address. Therefore as long as the name doesn't resolve then the client will connect.

You need to ensure that Autodiscover is working correctly, and that the client can indeed resolve the server's external address and connect.
0
 

Author Comment

by:ivolach
ID: 41816231
The client can resolve the server external address and the Autodiscover is working correctly for all other users.
Is there a way to reset the Autodiscover / Outlook anywhere settings just for this user?
0

Featured Post

Does Powershell have you tied up in knots?

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

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Finding original email is quite difficult due to their duplicates. From this article, you will come to know why multiple duplicates of same emails appear and how to delete duplicate emails from Outlook securely and instantly while vital emails remai…
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel. This lets you automatically sync them with…

749 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