Re: OWA Logon Problem
- From: "ACE-Joe" <ACEJoe@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 2 Jun 2005 07:07:14 -0700
One thing I am thinking is maybe its because the old mail server was a domain
controller. The new mail server is NOT. So would it be possible to make our
IMC server that is currently running Exchange 2003 Enterprise a Domain
Controller, keep it as our IMC and also use it as a front end server for OWA?
Or would making it a domain controller kind of nullify the whole security
reason for using a front end server? In the long run it will make things
easier for our end users, but it might be just as good to start having them
use their e-mail address or domain\username instead of going through all this
trouble.
Thanks
Joe
"Ben Winzenz [Exchange MVP]" wrote:
> With Exchange 200x, the authentication format is domain\username. This is
> your problem. Try using domain\username the first time you log in and see
> if that works.
>
> If you change the default domain listed under the authentication methods to
> either \ or the actual NetBIOS name of your internal domain, entering just
> username and password may work, but I wouldn't count on it to work 100% of
> the time - at least that is my experience. Having a FE server likely will
> make no difference.
>
> --
> Ben Winzenz
> Exchange MVP
> MessageOne
>
>
> "ACE-Joe" <ACEJoe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C84CCD30-E2EB-4AE3-8AB8-0137E9EBC720@xxxxxxxxxxxxxxxx
> > Ok, here is the deal. I have three exchange servers, all running 2003
> > Enterprise edition. I have one that we are phasing out, lets call it
> > server1, we moved all the mailboxes off this server to a new mail server
> > and
> > will be taking it down shortly. OWA was running off of Server1. We have
> > Server2 which is the new mail server that now houses all the mailboxes and
> > where we want OWA to work from now. We have Server3 that is our IMC and
> > not
> > hosting any mailboxes. Right now we have mail.server2.domain.com/exchange
> > setup for OWA access on our new mail Server2. Upon trying to logon after
> > entering your username and password, you are again prompted with the logon
> > box, this time it prepends your username with mail.domain.com and will not
> > authenticate you. You can manually edit the prefix to just the Active
> > Directory domain name, and it works, but this is a major pain for our
> > remote
> > users who now have to logon twice and don't know what the heck they are
> > doing. Now The public IP address used for OWA actually points to another
> > box
> > alltogether and our firewall re-directs traffic based on port number, so
> > when
> > OWA traffic hits our firewall it re-directs it to the new mail server2.
> > Which should work ok and it does seem to as we get the logon prompt for
> > OWA,
> > but this double authentication problems has to go away. Its like OWA is
> > not
> > using the default domain name I specified in my config, its trying to
> > check a
> > user database on the local machine, not on the domain. Exchange is not on
> > a
> > domain controller.
> >
> > So my question would be could we setup our Server3 as a front end server
> > and still use it as an IMC, but use OWA from Server3 and get the logon
> > problem fixed or is there a simple way to fix the problem and leave OWA
> > pointing to Server2?
> >
> > Thanks guys
> > Joe
>
>
>
.
- Follow-Ups:
- Re: OWA Logon Problem
- From: BSchmidt
- Re: OWA Logon Problem
- References:
- OWA Logon Problem
- From: ACE-Joe
- Re: OWA Logon Problem
- From: Ben Winzenz [Exchange MVP]
- OWA Logon Problem
- Prev by Date: Assign an AD group 'Full Mailbox Rights' to all users in OU
- Next by Date: Re: Public Folders
- Previous by thread: Re: OWA Logon Problem
- Next by thread: Re: OWA Logon Problem
- Index(es):
Relevant Pages
|
Loading
