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

OWA 2007- Forms Based Auth - 440 login timeout

When I enable forms based authentication (and reset IIS) in OWA 2007,
I get the following msg: 440 login timeout But when I changed it back to Intregared windows auth, it works fine..
I would like to use Form Based auth, does anyone know why this is occuring ?
Thanks
Liam
0
paadmin
Asked:
paadmin
  • 4
  • 2
2 Solutions
 
ATIGCommented:
have you added a cert to IIS?
0
 
paadminAuthor Commented:
Hey Brian,

Yes we are using a GoDaddy SSL cert...

Thanks for your help
Liam

 
0
 
ATIGCommented:
Liam, hello again :)

What all is on the CAS?
CAS,hub,mbx?

Did you delete anything or change things in IIS?

what all has been done to this box?
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
paadminAuthor Commented:
Hey Brian,

We have jsut one exchange 2007 server and all roles are installed on that. We do not have an edge transport server.

I do not believe that I deleted anything in IIS but during the course of the last few weeks, we have changed quite a few settings to get, activesync,autodisover and everything else...

Everything appears to be working perfectly now except forms based auth..

Thanks agian for your help, this is kind of a lower priority for me but I'd love to get it working..

Thanks
Liam

0
 
mrpez1Commented:
This happened to me. Turned out after I botched a modification to login.asp in c:\Program Files\Exchsrvr\exchweb\bin\auth\usa I copied back in a backup copy I had made. This screwed up the security permissions. Go to the security settings on the auth directory and under advanced reset the permissions on the child objects.
0
 
paadminAuthor Commented:
This issue got a whole lot worse today, when I arrvied to work, OWA  was not working (corrupt or something)..

see posting :
http://www.experts-exchange.com/Software/Server_Software/Web_Servers/Microsoft_IIS/Q_22853945.html

Now I cannot open OWA at all, 440 login timeout.

In responce to mrpexz1: I cannot locate the advacned directory.

If anyone else has a solution or soemthing I can try,  I will try it..  


0
 
paadminAuthor Commented:
The original issue is still not resovled I have gotten OWA working again by removing and adding Virtual OWA directories, I am clsoing this thread as I have read that their is not current solution to his issue. I  will continue to research.

0

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

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