Prev: IMCEAMAILTO
Next: Autodiscover issue
From: Maverick on 25 Jan 2008 17:06 I have an NLB CAS setup and have recently run into OOF and AS not working anymore via Outlook 2007. When I do a test-outlookwebservices -id user | fl, all tests come back fine on the CAS servers. However, when I run the autoconfiguration test via Outlook 2007, I fail to connect to the SCP. If find the SCP find but fails with an error of (0x800c8203). The funny thing is, I have temporarily mailbox-enabled a domain admin acct and the Outlook autoconfiguration test comes back fine and displays all the proper URLs (oab, UM, AS). Based on this, I figure it's got to be a permission issue but can't seem to find out where the permissions changed. I recently upgraded all of the mail servers to SP1 and this seems to be the time that AutoDiscover broke. This may just be a coincidence. Any thoughts would be great! Thanks.
From: Andy David {MVP} on 25 Jan 2008 17:22 On Fri, 25 Jan 2008 14:06:01 -0800, Maverick <maverick(a)falsedomain.donotspam.com> wrote: >I have an NLB CAS setup and have recently run into OOF and AS not working >anymore via Outlook 2007. When I do a test-outlookwebservices -id user | fl, >all tests come back fine on the CAS servers. However, when I run the >autoconfiguration test via Outlook 2007, I fail to connect to the SCP. If >find the SCP find but fails with an error of (0x800c8203). > >The funny thing is, I have temporarily mailbox-enabled a domain admin acct >and the Outlook autoconfiguration test comes back fine and displays all the >proper URLs (oab, UM, AS). Based on this, I figure it's got to be a >permission issue but can't seem to find out where the permissions changed. I >recently upgraded all of the mail servers to SP1 and this seems to be the >time that AutoDiscover broke. This may just be a coincidence. Any thoughts >would be great! Thanks. If you do a Get-ClientAccessServer , what does the AutoDiscoverServiceInternalUri point to?
From: Maverick on 25 Jan 2008 17:31 Hi Andy, The uri points to https://mail.domain.com/autodiscover/autodiscover.xml where mail.domain.com is the name of my NLB. Thanks for the reply. Maverick "Andy David {MVP}" wrote: > On Fri, 25 Jan 2008 14:06:01 -0800, Maverick > <maverick(a)falsedomain.donotspam.com> wrote: > > >I have an NLB CAS setup and have recently run into OOF and AS not working > >anymore via Outlook 2007. When I do a test-outlookwebservices -id user | fl, > >all tests come back fine on the CAS servers. However, when I run the > >autoconfiguration test via Outlook 2007, I fail to connect to the SCP. If > >find the SCP find but fails with an error of (0x800c8203). > > > >The funny thing is, I have temporarily mailbox-enabled a domain admin acct > >and the Outlook autoconfiguration test comes back fine and displays all the > >proper URLs (oab, UM, AS). Based on this, I figure it's got to be a > >permission issue but can't seem to find out where the permissions changed. I > >recently upgraded all of the mail servers to SP1 and this seems to be the > >time that AutoDiscover broke. This may just be a coincidence. Any thoughts > >would be great! Thanks. > > > If you do a Get-ClientAccessServer , what does the > AutoDiscoverServiceInternalUri point to? > >
From: Andy David {MVP} on 26 Jan 2008 09:24 On Fri, 25 Jan 2008 14:31:01 -0800, Maverick <maverick(a)falsedomain.donotspam.com> wrote: >Hi Andy, > >The uri points to https://mail.domain.com/autodiscover/autodiscover.xml >where mail.domain.com is the name of my NLB. hmmm, well assuming DNS is correct, you may want to run Exbpa against the org doing the permission check. Havent seen your error before. > >Thanks for the reply. > >Maverick > >"Andy David {MVP}" wrote: > >> On Fri, 25 Jan 2008 14:06:01 -0800, Maverick >> <maverick(a)falsedomain.donotspam.com> wrote: >> >> >I have an NLB CAS setup and have recently run into OOF and AS not working >> >anymore via Outlook 2007. When I do a test-outlookwebservices -id user | fl, >> >all tests come back fine on the CAS servers. However, when I run the >> >autoconfiguration test via Outlook 2007, I fail to connect to the SCP. If >> >find the SCP find but fails with an error of (0x800c8203). >> > >> >The funny thing is, I have temporarily mailbox-enabled a domain admin acct >> >and the Outlook autoconfiguration test comes back fine and displays all the >> >proper URLs (oab, UM, AS). Based on this, I figure it's got to be a >> >permission issue but can't seem to find out where the permissions changed. I >> >recently upgraded all of the mail servers to SP1 and this seems to be the >> >time that AutoDiscover broke. This may just be a coincidence. Any thoughts >> >would be great! Thanks. >> >> >> If you do a Get-ClientAccessServer , what does the >> AutoDiscoverServiceInternalUri point to? >> >>
From: Maverick on 28 Jan 2008 11:46
Hi Andy, Thanks for all of your help. Unfortunately, I still don't have this issue corrected. I may have to call PSS. Either way, much appreciated. "Andy David {MVP}" wrote: > On Fri, 25 Jan 2008 14:31:01 -0800, Maverick > <maverick(a)falsedomain.donotspam.com> wrote: > > >Hi Andy, > > > >The uri points to https://mail.domain.com/autodiscover/autodiscover.xml > >where mail.domain.com is the name of my NLB. > > hmmm, well assuming DNS is correct, you may want to run Exbpa against > the org doing the permission check. Havent seen your error before. > > > > >Thanks for the reply. > > > >Maverick > > > >"Andy David {MVP}" wrote: > > > >> On Fri, 25 Jan 2008 14:06:01 -0800, Maverick > >> <maverick(a)falsedomain.donotspam.com> wrote: > >> > >> >I have an NLB CAS setup and have recently run into OOF and AS not working > >> >anymore via Outlook 2007. When I do a test-outlookwebservices -id user | fl, > >> >all tests come back fine on the CAS servers. However, when I run the > >> >autoconfiguration test via Outlook 2007, I fail to connect to the SCP. If > >> >find the SCP find but fails with an error of (0x800c8203). > >> > > >> >The funny thing is, I have temporarily mailbox-enabled a domain admin acct > >> >and the Outlook autoconfiguration test comes back fine and displays all the > >> >proper URLs (oab, UM, AS). Based on this, I figure it's got to be a > >> >permission issue but can't seem to find out where the permissions changed. I > >> >recently upgraded all of the mail servers to SP1 and this seems to be the > >> >time that AutoDiscover broke. This may just be a coincidence. Any thoughts > >> >would be great! Thanks. > >> > >> > >> If you do a Get-ClientAccessServer , what does the > >> AutoDiscoverServiceInternalUri point to? > >> > >> > |