RE: username format for OWA "DC or Member server"



Sorry to say now, I haven't had much of a responcse at all. I've heard some
people say that they had the same problem, some say they can still use the
original username and password even after moving from a DC to a standalone.
To me it makes sense, if your using OWA and your server was a DC, then
demoted to a member server, when it tries to authenticate you it no longer
has a local copy of the directory data. So it will require more than just a
username and password to authenticate you, it needs to know the domain too.
There is a spot to specify a default domain in the OWA settings somewhere,
but that didn't work for me either. Its a pain for users, but makes sense to
me as to why it happens. Let me know if I can help anymore.

Thanks
Joe

"Heather" wrote:

> Joe, have you had any help or got any further with this issue? Reason I ask
> is that we are having similar problems and our situation is that we have also
> changed the Exchange server from being on a DC to having its own server.
> I would be really interested to hear more on this subject!
> Thanks
> Heather
>
> "TA-Joe" wrote:
>
> > Hi all!
> >
> > This is more for confirmation on my part than a real question. Here is
> > what I have observed regarding the required format of the username in OWA
> > when Exchange is on a domain controller or not.
> >
> > Scenario 1:
> > Exchange 2003 installed on Windows 2000 server in a 2003 Active Directory
> > Domain. Server is a domain controller. When users use OWA and login, they
> > can use this format for their login:
> >
> > username
> > password
> >
> > Scenario 2:
> > Exchange 203 is installed on a Windows Server 2003 Member server in a
> > 2003 Active Directory domain. When users use OWA and try to login with:
> >
> > username
> > password
> >
> > they get re-prompted for their logon credentials. Only the following will
> > allow a logon to OWA:
> >
> > domain\username
> > password
> >
> > or
> >
> > username@xxxxxxxxxx
> > password
> >
> > Just using your username no longer worked for me when Exchange was moved off
> > of a domain controller.
> >
> > My reasoning on this would be that when Exchange was installed on a DC,
> > it knew that user by the username only because it was a DC, it didn't need
> > to know the domain or the users e-mail to authenticate. When we moved
> > Exchange 2003 to a member server, who was not a DC, and did know all the
> > users on the domain, we started getting prompted for domain\username or
> > username@xxxxxxxxxxx
> >
> > I posted info about this before and no one seemed to understand or if
> > they did, had never seen this first hand.
> >
> > Is the above expected behavior (I think it is)? It makes sense to me,
> > but others have disagreed with me. Anyone care to comment or share their
> > thoughts on this.
> >
> > Thanks
> > Joe
.



Relevant Pages

  • Re: SBS2k Exchange recovery - HELP!
    ... as it pulls mail out into a SQL database. ... I discovered something else I didn't know about Exchange.. ... If I could have got OWA working from the RDP into the Server (so only ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Exchange 2003 OWA
    ... Please check SMTP addresses setting for Exchange Virtual Server ... Path" of the OWA virtual server he/she is trying to use. ... Install MBExplorer by installing IIS 6 Resource Kit Tools:http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71 ... ...
    (microsoft.public.windows.server.sbs)
  • RE: OWA HTTP 500 Error for users, but not for Admin (?)
    ... None of the previously added users can see the right side panel in OWA ... Exchange Server via OWA, you cannot see the right pane in OWA; ... Right click on Exchange virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook Web Access!!
    ... > protect Exchange server in four different ways. ... you can implement Exchange RPC filtering. ... > Third, if you use OWA, you can use ISA servers http filtering to protect the ...
    (microsoft.public.security)
  • Re: Outlook Web Access!!
    ... > protect Exchange server in four different ways. ... you can implement Exchange RPC filtering. ... > Third, if you use OWA, you can use ISA servers http filtering to protect the ...
    (microsoft.public.win2000.security)