Link to home
Start Free TrialLog in
Avatar of RyanHenry
RyanHenryFlag for United States of America

asked on

Auto Discover Outlook issues within LAN.

All,

I have an issue with Auto Discover not letting half of my users use their Out Of Office tool through the outlook client.  We host exchange through Rackspace, and they tried testing one of my failed users and they were able to use OOO just fine.  We verified that DNS Auto discover is correct at Rackspace.  They said the issue in on my LAN somewhere.  The strange part is if I switch to my wifi connection, then OOO works for all the users that are having the problem.  My wifi is plugged directly into my Cisco firewall on its own private subnet.  We are very small so all the users on my LAN are in the same subnet, there is only one for about 15 people.  

I tried plugging my RJ45 cable into the switch directly, and still I don't get though to Auto Discover and OOO.  I am not sure where to check next to try and see what is going on.

My network is  a Comcast Router, to a Cisco ASA 5512-X Firewall, to 2 Cisco 2960s switches (no VLANS)...  Any help would be appreciated?  Thx...
OOO-ERROR-1.png
ASKER CERTIFIED SOLUTION
Avatar of Jakob Digranes
Jakob Digranes
Flag of Norway image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of RyanHenry

ASKER

Thx for the help!!!  SO this is strange, CTRL Auto Config test fails on both working and non working PC's. However exchange web services test works on both Working & NON-Working PC??

One thing I noticed is it looks like redirect auto discover URL is still pointing towards "autodiscover.Mex07a.emailsrvr.com" on the failed pc and "secure.autodiscover.emailsrvr.com" on the good pc.
 
The change I made at rackspace dns was just "autodiscover.emailsrvr.com"

Attached are the return results.  Please let me know if you have any other ideas?  Could I also need to change my Local DNS record on my LAN Domain Controller?  This might make sense why if I use wifi, and skip the domain it works just fine?  But I am unsure of this, just thinking out loud?

l tested this from wifi and attach those results too!  Each screen shot will be labeled "Log,Results, and Good or Error"
Note, the Good ones that worked, were all using WiFi, otherwise it fails.
OOO-Results-test-auto-GOOD.PNG
OOO-LOG-test-auto-GOOD.PNG
OOO-Log-test-auto-error.PNG
OOO-Web-Services--test-GOOD.JPG
I figured out the issue.  I was just my local DNS record still using the old address.  Made the change to the record and flushed dens and all is good.  Thanks for the help though!
Was just a DNS issue
great it was solved :)