I'm sure this has been asked a thousand times here, and I've even read some of the posts along with the MS KB article on how to fix it, but nothing seems to be working.
What happened was that we installed a new Exchange 2007 member server and moved all the mailboxes from the old one (which also happened to be a domain controller) to the new server, and then decommissioned the old Exchange 2007/DC. A few weeks later we noticed that OWA was just saying "440 Login Timeout". Going through the instructions, resetting IUSR and IWAM passwords and such, what I have found is that sometimes, for a single login, it will actually work, but then will then start complaining about invalid security settings, which I assume relate to the directory security settings, even though I'm using the Powershell scriptlets that the KB article and other sites indicate what is needed to recreate the OWA web structure.
I'm at my wits end here. I just keep doing the same thing over and over again, and with the same result.
I'm sure this has been asked a thousand times here, and I've even read some of the posts along with the MS KB article on how to fix it, but nothing seems to be working.
What happened was that we installed a new Exchange 2007 member server and moved all the mailboxes from the old one (which also happened to be a domain controller) to the new server, and then decommissioned the old Exchange 2007/DC. A few weeks later we noticed that OWA was just saying "440 Login Timeout". Going through the instructions, resetting IUSR and IWAM passwords and such, what I have found is that sometimes, for a single login, it will actually work, but then will then start complaining about invalid security settings, which I assume relate to the directory security settings, even though I'm using the Powershell scriptlets that the KB article and other sites indicate what is needed to recreate the OWA web structure.
I'm at my wits end here. I just keep doing the same thing over and over again, and with the same result.
Just bumping this. It seems to be an obscenely common problem with Exchange 2007, but we are really in quite a bind over it, and I want to avoid going through the reinstall process if at all possible. Is there any solution?