Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
OWA
0 views
Skip to first unread message
Rodders
May 16, 2003, 11:42:19 AM5/16/03
to
I have installed Outlook web access on a domain controller
that is also running Exchange5.5 with latest service pack
and also IIS. When i try to to connect to
http://servername/exchange.... I get the logon page. I
then enter my alias which then takes me to me
authentication box. I enter my NT username and password
and get the following error.... Failed to connect to the
microsoft exchange server, "servername" [Collaboration
data objects -[MAPI_E_NOT_FOUND
(8004010F)]] /exchange/usa/logonfrm.asp
Any ideas???
that is also running Exchange5.5 with latest service pack
and also IIS. When i try to to connect to
http://servername/exchange.... I get the logon page. I
then enter my alias which then takes me to me
authentication box. I enter my NT username and password
and get the following error.... Failed to connect to the
microsoft exchange server, "servername" [Collaboration
data objects -[MAPI_E_NOT_FOUND
(8004010F)]] /exchange/usa/logonfrm.asp
Any ideas???
Bruce R.
May 16, 2003, 7:56:24 PM5/16/03
to
I am running sbs 2000 and have just uninstalled ISA Server. Now Outlook Web
Access doesn't work. Any ideas of what reconfiguration I need to do to get
it to work? Everything else seems okay.
Thansk
Bruce
Access doesn't work. Any ideas of what reconfiguration I need to do to get
it to work? Everything else seems okay.
Thansk
Bruce
Nathan
May 18, 2003, 3:14:06 PM5/18/03
to
Did you try the AD Connector tool to synch your accounts?
nathan
>.
>
Matthew Penney
May 21, 2003, 11:27:52 PM5/21/03
to
You can't use OWA on a Domain Controller. THe reason for this is that OWA
requires a "Log on Locally" right, and in a Domain Controller, there are not
Local Accounts, and therefore no Log on Locally Right. The only solution
would be to give everyone rights to logon interactively, which would pose a
security threat.
requires a "Log on Locally" right, and in a Domain Controller, there are not
Local Accounts, and therefore no Log on Locally Right. The only solution
would be to give everyone rights to logon interactively, which would pose a
security threat.
Matt
"Rodders" <rob.bea...@wymas.nhs.uk> wrote in message
news:014b01c31bc1$bc4ce560$a101...@phx.gbl...
0 new messages