doboszb
asked on
Free/Busy, Autodiscover and Out of Office not working in Exchange/Outlook 2007
Bookmark:Question: Here is the problem we are having, all of a sudden the Free/Busy, Autodiscover and Out Of Office are not working on our three Citrix Servers. It works for everyone else in the company so we know it isn't a problem with out Exchange Server and the odd thing is if I run Outlook from a local session on the Citrix server everything works correctly, if I use the same account and try and run Outlook through Citrix on the same server it doesn't work.
Does anyone have any ideas on what the problem could be? I am stuck at this point. We are running Exchange and Outlook 2007 on all machines. I have also included the log files from both the local and Citrix sessions on a server using the same account.
Hope you guys can help me out on this one!
local.log
Citrix.log
Does anyone have any ideas on what the problem could be? I am stuck at this point. We are running Exchange and Outlook 2007 on all machines. I have also included the log files from both the local and Citrix sessions on a server using the same account.
Hope you guys can help me out on this one!
local.log
Citrix.log
ASKER
The free/busy says "No/Free Busy Information could be retrieved" The Out of Office say "Your Out of Office settings cannot be displayed, because the server is unavailable. Try again later". And the feature where when you launch Outlook 2007 for the first time and it fills in your account information for you doesn't work as well, you need to manually put in the mail server and username when setting up a new users.
Like I said before this is only happening to users connected to Citrix sessions on our three Citrix servers. I did some testing yesterday and it appears for some reason that these users are hitting a different forward lookup zone in DNS. I didn't setup our DNS but there are two zones, one is company.us and the other one is company.com. For some reason the Citrix users are hitting the company.us zone instead of the company.com zone that has all the dns records in it.
The wierd thing is this just started happening and nothing was done to any of the three Citrix servers. We have a test citrix server where all three features work correctly through Citrix sessions. We are just stuck at this point......
Like I said before this is only happening to users connected to Citrix sessions on our three Citrix servers. I did some testing yesterday and it appears for some reason that these users are hitting a different forward lookup zone in DNS. I didn't setup our DNS but there are two zones, one is company.us and the other one is company.com. For some reason the Citrix users are hitting the company.us zone instead of the company.com zone that has all the dns records in it.
The wierd thing is this just started happening and nothing was done to any of the three Citrix servers. We have a test citrix server where all three features work correctly through Citrix sessions. We are just stuck at this point......
Where do the users have email addresses? The errors all point to the same thing, the lack of either the DNS settings for web services or they are not running.
If the user have email addresses in the company.us zone then you should have autodiscover.company.us in there that points to the Exchange server.
-M
If the user have email addresses in the company.us zone then you should have autodiscover.company.us in there that points to the Exchange server.
-M
ASKER
All users do have a company.us email address. But if there has to be an autodiscover.company.us then how is it working for everyone else who isn't in a Citrix session on that server?
I can't answer that. I haven't got a Citrix environment I can look at.
All I can work on is the symptoms that you have posted, which point to Outlook being unable to find the web services that it requires, which usually revolve around the autodiscover.domain.com URL pointing to the Exchange server.
-M
All I can work on is the symptoms that you have posted, which point to Outlook being unable to find the web services that it requires, which usually revolve around the autodiscover.domain.com URL pointing to the Exchange server.
-M
ASKER
If I put an autodiscover in the the company.us zone its throwing up a security alert about a certficate.
ASKER
Citrix Session:
Autodiscover to https://company.us/autodiscover/autodiscover.xml starting
Autodiscover to https://company.us/autodiscover/autodiscover.xml FAILED (0x800C8203)
Server Session and all other users:
Attempting URL https://mail.company.us/autodiscover/autodiscover.xml found through SCP
Autodiscover to https://mail.company.us/autodiscover/autodiscover.xml starting
When I look at the Outlook logging for the two differenet sessions the first two lines are very different. The Citrix session that doesn't work is looking for company.us and all the rest are looking for mail.company.us.
Is there a reason for this?
Autodiscover to https://company.us/autodiscover/autodiscover.xml starting
Autodiscover to https://company.us/autodiscover/autodiscover.xml FAILED (0x800C8203)
Server Session and all other users:
Attempting URL https://mail.company.us/autodiscover/autodiscover.xml found through SCP
Autodiscover to https://mail.company.us/autodiscover/autodiscover.xml starting
When I look at the Outlook logging for the two differenet sessions the first two lines are very different. The Citrix session that doesn't work is looking for company.us and all the rest are looking for mail.company.us.
Is there a reason for this?
ASKER
Ok I have done some more testing and I found out that all external users using Outlook Anywhere are having the same problem. I understand it may be a cert problem (currently we only have a cert with one name on it "mail.company.us" and I have read we need one that also have autodiscovery.company.us.
For some reason it is treating all internal Citrix users like they are external, any idea of why?
For some reason it is treating all internal Citrix users like they are external, any idea of why?
If you only have a single name SSL certificate then you do not have a valid certificate for Exchange 2007. You really need a SAN/UC certificate with the additional names in it of the external host name, autodiscover plus the server's NETBIOS name and FQDN.
If you have more than one domain then really you should have autodiscover.domain.com for each domain in there as well.
It is possible to use a single name SSL certificate, however for it to work correctly you have to create SRV records in your DNS. That can be done for internal DNS because Windows DNS supports it, but for external domains not all domain name registration servers support it.
From memory it goes through
domain.com
autodiscover.domain.com
mail.domain.com
So that would be why it is working for some users. However things aren't quite right with your setup, so inconsistent results would be expected.
-M
If you have more than one domain then really you should have autodiscover.domain.com for each domain in there as well.
It is possible to use a single name SSL certificate, however for it to work correctly you have to create SRV records in your DNS. That can be done for internal DNS because Windows DNS supports it, but for external domains not all domain name registration servers support it.
From memory it goes through
domain.com
autodiscover.domain.com
mail.domain.com
So that would be why it is working for some users. However things aren't quite right with your setup, so inconsistent results would be expected.
-M
ASKER
It's not really inconsistent, all internal users can use Out of Office and see Free/Busy except for our three Citrix servers. For some reason they can reach the SCP record in AD. I just built a new Citrix server today that is identical to the other three and it works perfectly. Something happened with the other three for some reason and I am not sure how to correct it besides making new servers.
The fact that is has happened to three servers would tend to point something at the network level. Not really sure what it could be, because it is working elsewhere.
Something new installed on all of the servers? Doing something network wise for the Citrix servers that may not have taken on the new server yet?
-M
Something new installed on all of the servers? Doing something network wise for the Citrix servers that may not have taken on the new server yet?
-M
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you provide the KB #?
ASKER
There was no KB# for this issue, I figured it out myself by uninstalling Hotfix 3 and everything worked correctly again
Although all three parts are all dependant on web services, so that would tend to point to the source of the problem. However that would not explain why it only fails in the session and not on the server itself.
-M