[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 448
  • Last Modified:

OWA asks for login credentials each time user tries to open an email

Hi all,  My user can login into OWA fine from IE 6, the problem occurs when he tries to read his email.  Each time he opens an email, the login box pops up and asks for his login again.  I went to a different computer and everything works just fine.  The problem only occurs on his latop.  

Latop is XP Home edition SP1

Server is SBS 2000

thanks in advance for your help!
  • 2
1 Solution
1. He may not have session cookies enabled in the IE security tab (Custom/enable session cookies)..
2. Is he logged onto the LAN or working remotely when this happens?
3. Are you trying to reproduce the problem from inside or outside of the network?

You may have directory security enabled in IIS, in which case only users outside the domain would experience this problem.  

Also, you may wish to enable forms based authentication, this will require SSL though if you don't already have it set-up, you probably should.  No, you really should!  Forms based authentication is setup in the Protocols/HTTP properties in ESM..  This will enable session cookies for the logged in user.

Hope that helps.
bobbit31Author Commented:
He is logins in remotely and when I tested this, I have done it from remote computers.  All other users are fine except for him.  I will try your suggestions and let you know if they work.  Thanks
This may sound silly as I was looking for an answer to a similar problem I was having here.  I just discovered that this user had a contact object created when he used to be in another branch office of ours.  And now that he is here he had a local account created in this domain but the contact object was never deleted.  He is the only user I have that was having this problem and this was the only difference I have found so far.  I'll know soon if this has fixed his problem.  
Deleting the contact object that had the same name as his user id obect was causing this issue with him.  Our environment is as follows.   Inbound traffic on 443 through firewall to Pound proxy box and openssl ==> port 80 traffic b/t pound box and owa running E2K in E2K Environment.   Server is W2K SP4 with E2K and laters post SP3 rollup package.   Don't know if you'll have the same problem.

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now