Pro-Exchange,Lync & Office 365
Belgian Microsoft Unified Communications Professionals
Microsoft Exchange Server, Microsoft Lync Server & Office 365

autodiscovery not working for some users only

rated by 0 users
This post has 5 Replies | 3 Followers

Top 10 Contributor
Posts 25
Points 590
dgoossens Posted: 12-16-2010 6:23

Hello,


I'm experiencing a problem for some users who can't see freebusy info in outlook 2007.
When checking I also noticed they have problems downloading the OAB.

The problem is caused by autodiscover which isn't working correctly.

The strange thing is that it's only for some users.
VIa webmail all is OK.

When I create a new mail profile, it takes very long, but eventually it gets configured without me having to configure it manually. So does it mean it's very very slow, or does it get configured in another way?

I've checked DNS settings and these are all the same on the computers.
DNS suffix etc are the same too.
dns resolving of the mailservers is Ok too.
I tried disabling the auto detect in iexplorer > same problem

We do use ISA in the autodetect.


 

 

Top 10 Contributor
Posts 391
Points 8.000

These users have the same email address?
Also on the same Exchange mailbox server?

  • | Post Points: 30
Top 10 Contributor
Posts 25
Points 590

yes, they're all located on the same server, and are using the same @client.be type address.
Via webmail all is going perfectly (they can view freebusy), but autodiscover seems to be failing.
They're also all on the same subnet.

  • | Post Points: 10
Top 10 Contributor
Posts 25
Points 590

I've opened up an MS ticket, so I'll let you know when I have a resolution

  • | Post Points: 10
Top 75 Contributor
Male
Posts 2
Points 60

Dgossens,

I would start with checking your autodiscover configuration using the following Exchange connectivity tool.

 

https://www.testexchangeconnectivity.com/

Let me know what the results are.

 

  • | Post Points: 30
Top 10 Contributor
Posts 25
Points 590

hey Jason,

For all other users autodiscovery is working correctly, but for some it doesn't.
I've been on the phone with MS yesterday (2 MS engineers), but they couldn't find the solution yet.

I've received some regkeys that I should configure, maxpacketsize and length.
> lsas, and http
But for that I still need to reboot the servers.
I don't think this'll fix the issue, but we'll see. :-)

  • | Post Points: 10
Page 1 of 1 (6 items) | RSS