[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1763
  • Last Modified:

Outlook 2007 Autodiscover Not Working (Non-Domain Client)

Hi,

We've recently migrated over from SBS 2003 to SBS 2008. We have 5 domain-joined PC's running Outlook 2007 - these are working fine.

However, we have one laptop that in not joined to the domain (Home O/S) - this laptop is unable to download the Offline Address Book, nor set Out Of Office. I'm convinced that this is to do with the Autodiscover feature as if the Outlook Autoconfiguration test fails with "unable to determine settings".

Also, if I try to browse to the autodiscover URL (https://remote.domain.com/autodiscover/autodiscover.xml) I am prompted for a user name and password. This doesnt happen from a domain-joined PC. Once the creditials are entered the XML data is displayed correctly.

I've carried out lots of google research but have now hit a dead end - I'm hoping that someone may have experience of this issue and offer a solution!

Any ideas?

Thanks,

Ben
0
TS_BenB
Asked:
TS_BenB
1 Solution
 
ricjeCommented:
Have you tried to rebuild the OAB?

Also have a look here:

http://www.exchangeninjas.com/AvailabilityServiceFAQ
0
 
TS_BenBAuthor Commented:
Yes I've tried this, though as I say - I think the problem lies in the inability to access the autodiscover/autodiscover.xml website (unless i'm missing something).

To recap - domain clients connect to the website ok, non domain clients do not (they are prompted for authentication).

Ben
0
 
endital1097Commented:
ensure that you have basic authentication enabled for your virtual directories

set-oabvirtualdirectory server\oab* -basicauthenication:$true
set-webservicesvirtualdirectory server\ews* -basicauthentication:$true
set-autodiscoveryvirtualdirectory server\auto* -basicauthentication:$true
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
TS_BenBAuthor Commented:
I've checked and this seems to all be set...

Ben
0
 
endital1097Commented:
i have to ask this, but is the certificate from a trusted certificate authority

when you browse to https://mail.contoso.com/owa from the non-domain client, do you get any certificate warnings
0
 
TS_BenBAuthor Commented:
Yes its a trusted cert - no prompts on accessing website...

Thanks,

Ben
0
 
rr1968Commented:
Try clicking the Outlook button from taskbar, while holding "CTRL" button and select "Test email auto-configuration" and select all the check boxes and just enterthe user's email address and press "test"
See if you find any issues there.

Did you try configuring Outlook anywhere or RPC over HTTPS from this WS?
0
 
TS_BenBAuthor Commented:
The auto config test fails saying "unable to determine auto configuration settings" (or words to that effect). Its when I saw that, that I tried to access the autoconfiguration.xml website and noticed the prompts for authentication (not seen on domain connected pcs).

The machine is already configured for outlook anywhere, should I try turning it off?

Thanks,

Ben
0
 
endital1097Commented:
take a look at the following for the configuration of autodiscover
http://www.shudnow.net/?s=autodiscoverserviceinternaluri
0
 
TS_BenBAuthor Commented:
Sorry for delayed reply..

i've actually already added a local dns autodiscover record and that works fine - this issue is that the non domain PC isnt able to access the autoconfiguration info (its prompted for authentication when accessing the autoconfiguration.xml website).

I want this to behave in the same way the domain PC's do - i.e. no authentication prompt and thus the ability to read the autoconfiration.xml page.

Ben
0
 
endital1097Commented:
basically your external/non domain accounts are going to attempt to connect to the autodiscover service using the following
https://domain.com/Autodiscover/Autodiscover.xml
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml

this requires your certificate on the cas server to have one of these two names unless your:
1. external DNS server has an SRV record for _autodiscover._tcp.domain.com that points to the A record of your CAS (ex. mail.domain.com)
2. your CAS server is configured with SSL certificate redirection (http://technet.microsoft.com/en-us/library/bb310764.aspx)
0
 
TS_BenBAuthor Commented:
Ok I see where you're coming from - our SSL cert is trusted but only for a single domain name... It looks like our domain provider supports SRV records so i'll set one up and see what happens.

Thanks,

Ben
0
 
endital1097Commented:
if you found that artilce helpful, please select that it was
thanks
0
 
TS_BenBAuthor Commented:
I'm afraid that I never got to test the solution properly as my client decided to replace the PC with one that was running a business O/S.

Nevertheless, I suspect that endital's suggestion my have worked and appriciate the help so points awarded.

Thanks,

Ben
0
 
TS_BenBAuthor Commented:
Wasnt able to fully test the solution provided so are unsure of its success.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now