Autodiscover broken internally-- Exchange 2010

We had a crash on our SBS 2011 regarding Exchange. After trying to upgrade to Exchange SP2 it failed and Exchange was not working. Microsoft stepped in to help and we were able to get Exchange back up and running.
Only problem now is that Autodiscover is not working internally. Users cannot set Automatic Replies internally. Externally it works fine and users can set Automatic replies from OWA.
We need to get the Autodiscover working internally. Any ideas?
Thanks
electricdadAsked:
Who is Participating?
 
hecgomrecConnect With a Mentor Commented:
Just replace the address in your DNS for the public IP with the Internal.


You can't give a resource and external IP (internet facing - public IP) as the firewall won't allow the package to pass.

This is a normal procedure when you have the same internal and external name for a server.
0
 
Simon Butler (Sembee)ConsultantCommented:
Run the fix my network wizard in the SBS management console. That will usually resolve most things. The main probably is probably around URLs or SSL certificates, which the wizard should correct.

Simon.
0
 
Carol ChisholmCommented:
Check your DNS. Make sure that the autodiscover URL resolves to the internal IP on the workstations.
0
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

 
electricdadAuthor Commented:
Well,
there is no autodiscover entry in DNS. Only the external DNS site has the entry for the public IP. Would I have to create a new zone? Thanks
0
 
Carol ChisholmConnect With a Mentor Commented:
you need the internal workstations to be able to find the internal IP of the exchange server.
If they try to go to the external address they will get confused.

Here is the Microsoft reference

http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx

And petri.com
http://www.petri.co.il/autodiscover-configuration-exchange-2010.htm
0
 
electricdadAuthor Commented:
Thanks guys,
I will try your suggestions and be back with you a little later.
0
 
Krishna PatilCommented:
0
 
electricdadAuthor Commented:
OK Hecgomrec and carolchi, I have created a DNS record and the autodiscover service appears to be working. I can setup an email account automatically now internally. But Automatic Replies still give an error-- Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again Later __
Outlook was restarted-- should I reboot the server? I restarted Information Store with no luck.
thanks
And Automatic Replies works fine externally for my account-- but a user is calling saying it is not working for hers remotely. ??
0
 
hecgomrecConnect With a Mentor Commented:
Make sure you don't have any other DNS record pointing to another IP.  DNS records are replicated among servers and a copy is store on the clients, you must run on clients on an elevated CMD, ipconfig /flushdns and then ipconfig /registerdns.  If this is not possible clients should reboot and try back.

If you are using outlook anywhere, this mean the client can't access the proxy (CAS) server with the previous settings.  First recommendation will be to re-create the profile.

In case you need more on info check this or here.
0
 
electricdadAuthor Commented:
I had just created a new profile and still not working. Cant see any other DNS records that are a problem. Autodiscover appears to be working since I can setup an email account automatically. But the Automatic Replies still gives this error internally??
0
 
electricdadAuthor Commented:
Uh Oh
Found a zone for Remote.domain.com in DNS and it referenced the Public IP. I changed it to the internal Exchange IP and it seems to be working-- I think my firewall was blocking the service from coming back in somehow or it did not know what to do with the public IP instead of the internal exchange IP. Seems to be working now!
Thanks for you help
0
 
Carol ChisholmCommented:
Well done. You had to find that external IP.
0
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.

All Courses

From novice to tech pro — start learning today.