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?
LVL 6
Sid_FAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JdtuckCommented:
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.
Shreedhar EtteTechnical ManagerCommented:
MegaNuk3Commented:
Can you paste a screenshot of the prompt?

Is it just a standard username/password prompt?
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

JoeBelliveauCommented:
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.
Sid_FAuthor Commented:
autodiscover
autodiscover.jpg
MegaNuk3Commented:
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.yourdomainname 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
Sid_FAuthor Commented:
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
MegaNuk3Commented:
Point it at an invalid IP address or a server that doesn't run iis.
MegaNuk3Commented:
Pointing it at an invalid/non routable IP address is what I would do though.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JoeBelliveauCommented:
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.
MegaNuk3Commented:
This is Exchange 2003 so there is no autodiscover...
JoeBelliveauCommented:
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.
MegaNuk3Commented:
You don't need a cert, you just need to stop autodiscover.yourdomain.com 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
JoeBelliveauCommented:
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.
Sid_FAuthor Commented:
thanks
MegaNuk3Commented:
Did you use a non routable IP address to resolve this or remove the catchall?

Thanks for the points by the way.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.