I searched around, but couldn't find anyone else having this problem. If this is addressed somewhere else, I'd appreciate the link! So... All of my users are on Outlook 2007 with Exchange 2007 SP1. One of my users is unable to obtain free/busy info. When he adds users to a meeting, a gray bar is displayed. After about a minute or so, it times-out and the lined, "no information" bar is displayed. I have a second use who has a similar problem, but before timing out, he does obtain the free/busy. It just takes a while. Any idea what might cause the free/busy to take a while to display? Where should I look for a problem? I'm at a loss, because everyone else seems fine and that's hundreds of users. Thanks! Tim

How about from OWA or logged onto another workstation? Same problem?Have you tried creating a new Outlook profile for this user? Are they in online or cache mode? ( If cache mode, delete the .ost and let Outlook recreate it)

Have you done a netstat -an and checked for anything that is in Syn Sent or Time_Wait. It may be trying to query something that it doesn't have access to, firewall or etc, and it's timing out. Can you have these users try a machine that is working fine and see if the same problem exists?Mark Morowczynski|MCT| MCSE 2003:Messaging, Security|MCITP:ES, SA,EA|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com

Mark and Andy, I'll try both of those. Both users are VPs, so I'm working around their schedules. Thanks for the input. I'll report back soon. We have already tried re-creating the OST file, /cleanfreebusy, and flipping out and back into cached. -Tim

Tried out the suggestions. Problem doesn't occur in OWA and is not local to the machine. I had some available cases, so I opened on. Right now, MS is looking at replication as a possible cause. I don't see that being a logical investigation, but I'll let them do whatever. Thanks for the suggestions. If there are any others, I'd love to hear them. -Tim

Update: When I first deployed Exchange 2007 I was going to use NLB for two CAS servers. I couldn't get that working so eventually abandoned it. I found a remnant of it on one of my cas. The Availability Service URL was https://cas.mydomain.com/EWS/Exchange.asmx instead of https://cas2.mydomain.com/EWS/Exchange.asmx. The other cas was fine, pointing to itself. So I fixed that. Now my users don't time out, but it can still take 30 seconds to display free/busy time.

Good find. What's the bandwidth between the user and the CAS? Mark Morowczynski|MCT| MCSE 2003:Messaging, Security|MCITP:EMA 2K7,EDA Win 7,ES,SA,EA|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com

100/Full LAN. Two CAS here in the same site. A third is in our DR site. Bandwidth to there is 10 Mbps. Are there any circumstances when a CAS from another site would be chosen over local?