OWA Login is beginning to fail

JTT · Joined: 06 Aug 2007 Posts: 7

We are running Exchange 2k on a Windows 2k domain. We have just one
Exchange server and the users have been using OWA with no problems until
recently. Now on some machines only the user that is logged into the domain
is the only one able to login to OWA, and they are now required to put in
the domain (which is set in the Exchange setup). However if we try logging
in with another account on that same machine with proper credentials we are
unable to log in.

Previously if the users went to http://servername/exchange then it would log
them in directly if they were logged into the domain. If we had them go to
http://alias.domain/exchange then it would prompt them for a username and
password and they would be able to log in.

I wish I could say there was some specific changed, unfortunately we have
several people in our IT department and a couple like to make undocumented
changes. I'm the person that is suppose to work on the Exchange server and
there's been no changes made by myself since the conversion to Exchange.

In help would be greatly appreciated...

JTT

Archived from group: microsoft>public>exchange>mobility

Peter O'Dowd · Joined: 06 Aug 2007 Posts: 1

Have you tried...
http://servername/exchange/username

It's not clear from below that you have...

Peter O'Dowd

"JTT" wrote in message@tk2msftngp13.phx.gbl...
> We are running Exchange 2k on a Windows 2k domain. We have just one
> Exchange server and the users have been using OWA with no problems until
> recently. Now on some machines only the user that is logged into the
domain
> is the only one able to login to OWA, and they are now required to put in
> the domain (which is set in the Exchange setup). However if we try
logging
> in with another account on that same machine with proper credentials we
are
> unable to log in.
>
> Previously if the users went to http://servername/exchange then it would
log
> them in directly if they were logged into the domain. If we had them go
to
> http://alias.domain/exchange then it would prompt them for a username and
> password and they would be able to log in.
>
> I wish I could say there was some specific changed, unfortunately we have
> several people in our IT department and a couple like to make undocumented
> changes. I'm the person that is suppose to work on the Exchange server
and
> there's been no changes made by myself since the conversion to Exchange.
>
> In help would be greatly appreciated...
>
> JTT
>
>

JTT · Joined: 06 Aug 2007 Posts: 7

We will try this but this won't solve the over all problem. We have several
users that are not technical, and we have a link from our Intranet that
points to the OWA that they click on or that one that was setup on their
local desktop.

The strange thing is it's only on a few machines that they are not able to
access OWA as a different user than the one that is logged in.

JTT

"Peter O'Dowd" wrote in message@TK2MSFTNGP11.phx.gbl...
> Have you tried...
> http://servername/exchange/username
>
> It's not clear from below that you have...
>
> Peter O'Dowd
>
> "JTT" wrote in message
> @tk2msftngp13.phx.gbl...
> > We are running Exchange 2k on a Windows 2k domain. We have just one
> > Exchange server and the users have been using OWA with no problems until
> > recently. Now on some machines only the user that is logged into the
> domain
> > is the only one able to login to OWA, and they are now required to put
in
> > the domain (which is set in the Exchange setup). However if we try
> logging
> > in with another account on that same machine with proper credentials we
> are
> > unable to log in.
> >
> > Previously if the users went to http://servername/exchange then it would
> log
> > them in directly if they were logged into the domain. If we had them go
> to
> > http://alias.domain/exchange then it would prompt them for a username
and
> > password and they would be able to log in.
> >
> > I wish I could say there was some specific changed, unfortunately we
have
> > several people in our IT department and a couple like to make
undocumented
> > changes. I'm the person that is suppose to work on the Exchange server
> and
> > there's been no changes made by myself since the conversion to Exchange.
> >
> > In help would be greatly appreciated...
> >
> > JTT
> >
> >
>
>

Albatross Singh · Joined: 06 Aug 2007 Posts: 1

Greetings Jason

Try the user authentication -> logon settings in the security options in
Internet Explorer.

Thanks
Albatross Singh

"JTT" wrote in message@tk2msftngp13.phx.gbl...
> We are running Exchange 2k on a Windows 2k domain. We have just one
> Exchange server and the users have been using OWA with no problems until
> recently. Now on some machines only the user that is logged into the
domain
> is the only one able to login to OWA, and they are now required to put in
> the domain (which is set in the Exchange setup). However if we try
logging
> in with another account on that same machine with proper credentials we
are
> unable to log in.
>
> Previously if the users went to http://servername/exchange then it would
log
> them in directly if they were logged into the domain. If we had them go
to
> http://alias.domain/exchange then it would prompt them for a username and
> password and they would be able to log in.
>
> I wish I could say there was some specific changed, unfortunately we have
> several people in our IT department and a couple like to make undocumented
> changes. I'm the person that is suppose to work on the Exchange server
and
> there's been no changes made by myself since the conversion to Exchange.
>
> In help would be greatly appreciated...
>
> JTT
>
>

Ciaran · Joined: 06 Aug 2007 Posts: 1

Easy way around the problem is get the users to use IP address instead of server name
http://x.x.x.x/exchange
instead of
http://servername/exchange

Hope it helps
Ciaran

MAPIInitialize(NULL) used to fail after 10-15 successfully a Hi Everyone, I posted a similer query 10 days back but there was no responce to that. here with i am resending similer query. please help in in resolving this issue. I am facing some issues with MAPI. I am trying to get mailbox information from 2000/2003

Help ! Exchange 2003 Database Mount fail.....EV ID : 9519 Even : Error 0xfffffde4 starting database "First Storage Group\Mailbox Store (HOME2003)" on the Microsoft Exchange Information Store. Run Eseutil /p : Microsoft(R) Exchange Server Database Utilities Version 6.5 Copyright (C) Microsoft Corporation. All Rig

440 Login Timeout I just upgraded Exchange 2000 to 2003 and Server 2000 to 2003. The original Exchange 2000 had OWA working with SSL. I'm now getting "440 Login Timeout" when I try to connect with OWA. Forms Based is enabled. SSL is configured in IIS. If

OWA Login Failures Win2K server, Exchange 5.5 SP4. Some of my users can use OWA from home and some cannot. All teachers have the same rights. After the third password try, they get the "You are not authorized to view this page" message. Any ideas why it works for some and n

OWA initial login attempt Hi, Fairly new at SBS 2003 Exchange OWA deployment. Single Server. Is it true that I should be able to go to from within the network and attach with administator? I use the correct URL and I receive a login box. SITE=server, REA