I'm having an issue with a small number of Outlook 2007 users.
When doing an Test E-Mail Auto Configuraiton, the Autodiscover URL times out, this is being discovered via SCP. However, the URL is correct and other Outlook 2007 clients are able to connect to the URL and publish other individuals free/busy informaiton and out of office assistant. For the users that cannot connect, their Outlook locks up when attempting to check these areas.
I checked the Exchange Server and the SCP urls check out and there isn't anything wrong with the services in IIS. This is obviously a client issue. However, when doing a Test-OutlookWebServices -identity "client" on the server all my clients that are having this problem, are checking out just fine. Also the same clients can access this information via OWA. Therefore, there is an issue with the local Autodiscover service (or so I believe). However, I've restarted Outlook with the /cleanfreebusy switch and the users in question still have this issue. Is there anything I'm missing here that I can do? I've got an autodiscover sub-domain in DNS and I've done everything short of SRV records but I dont' want to make major changes for a small section of clients.
Another key point. I can get it to work on one laptop but I cannot get it to work on another. I'm using my account as a test so the issue is at the specific client level but I'm not sure username has anything to do with it. It just may be local Outlook setting issues.
What could be the cause here as it's only affecting about 5 individuals of about 45 running Outlook 2007. Any help would be greatly appreciated. Thanks.