Sid_F
asked on
exchange 2003 with outlook 2007 autodiscover problem
I'm using outlook 2007 with exchange 2003 but getting an autodiscover prompt. How can I disable this?
Are you not using RPC over HTTP(s) with Exchange 2003? If not, you can disable it with a GPO or undo all the settings.
Hi,
Refer this:
https://www.experts-exchange.com/questions/24646697/How-to-disable-Outlook-2007-auto-discover.html
Hope this helps,
Shree
Refer this:
https://www.experts-exchange.com/questions/24646697/How-to-disable-Outlook-2007-auto-discover.html
Hope this helps,
Shree
Can you paste a screenshot of the prompt?
Is it just a standard username/password prompt?
Is it just a standard username/password prompt?
Turn off basic authentication on the virtual directory and make sure just windows auth is on, that solves the issue with it popping up. If it is indeed an auth request for Autodiscovery.
Look at the connection status menu and see if it is really that setting the pop up. Status will hang before it logs into the other objects if it is waiting on authorization for a service.
Look at the connection status menu and see if it is really that setting the pop up. Status will hang before it logs into the other objects if it is waiting on authorization for a service.
ASKER
autodiscover
autodiscover.jpg
autodiscover.jpg
Ping the autodiscover DNS name on the ssl cert prompt and verify if it is resolving to an address.
If it is resolving to a valid address then use nskookup to find out where it is getting that IP address from and remove the entry.
The other thing you can do as a test is add an invalid ip address for autodiscover.yourdomainnam e to the local HOSTS file and then outlook won't be able to resolve it to a valid server and you should not get the prompt
If it is resolving to a valid address then use nskookup to find out where it is getting that IP address from and remove the entry.
The other thing you can do as a test is add an invalid ip address for autodiscover.yourdomainnam
ASKER
ah ok now I'm getting some where. The internal dns domain is say internaldomain.local the email domain hosted by this exchange server is mycompany.com the cert is referring to autodiscover.mycompany.com I think the hosting company has a catch all rule for mycompany.com as the autodiscover.mycompany.com domain resolves to an external ip address. now to resolve it I'm thinking I can setup a secondary zone in dns on the local server for mycompany.com and create an A record for autodiscover.mycompany.com however where should I point this to or will this even resolve the problem. The quickest way would be to test but for the fact the autodiscover problem only pops up every few days and i want to try resolve it now.
Thanks
Thanks
Point it at an invalid IP address or a server that doesn't run iis.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
well it looks like you have to add autodiscover.domain.com to the cert so that the cert is considered valid for it.
Look in the alternate dns tag on the cert. That is where it should go, but a new cert has to be generated for this.
Look in the alternate dns tag on the cert. That is where it should go, but a new cert has to be generated for this.
This is Exchange 2003 so there is no autodiscover...
MegaNuk3 , this still doesn't stop the outlook client from trying to find an autodiscover path.
The folder does not have to be there the cert just has to be and a virtual directory can be made to stop the annoyance, the error will just show that autodiscover failed.
The folder does not have to be there the cert just has to be and a virtual directory can be made to stop the annoyance, the error will just show that autodiscover failed.
You don't need a cert, you just need to stop autodiscover.yourdomain.co m resolving and then there won't be a cert issue.
I have a client who runs exchange 2003 with outlook 2007 & 2010 clients and he gets no certificate prompts from either version of outlook and his cert is single name mail. Company.com which works for OWa, EAS & RPC / HTTPs
I have a client who runs exchange 2003 with outlook 2007 & 2010 clients and he gets no certificate prompts from either version of outlook and his cert is single name mail. Company.com which works for OWa, EAS & RPC / HTTPs
Then outlook hangs while failing to resolve the name.
Guess there is multiple ways of working around the issue. Either way it should work, let's hope it does for the user.
Guess there is multiple ways of working around the issue. Either way it should work, let's hope it does for the user.
ASKER
thanks
Did you use a non routable IP address to resolve this or remove the catchall?
Thanks for the points by the way.
Thanks for the points by the way.