I have a client and we have registered all accounts and we are able to get to the login screen, but when we enter our user info, and click OK it just sends us back to the login box, with no errors. We are going through HTTPS, but no one can log in. Any help?
By default you need to use the domain\username format. Does that work? If yes you need to changed the authentication settings for the OWA virtual directory in the Exchange Management Console in order to log in only using username.
_____________________________
HTH Henrik Walther Lead Moderator/author MSExchange.org
Yes. This is the way that it set and it is also the way that we are entering the User name, BUT unfortunitly we are still unable to get access to any of the email accounts . Any other opinions?
Internal clients work fine, but when an external client connects to owa they see the logon page. Yeah. But after logging in the user is redirected to logon page with no error message. If you login with a bad password it tells you ISA can not confirm you as a user.
I can not seem to get beyond this page. I look at the live monitor and it says everything is hunky dory.
These users are on the new Exchange 2007 server and we are using the domain\user standard.
Posts: 37
Joined: 16.Jul.2002
From: Rhode Island
Status: offline
I am having similar issues, except I am not using ISA server at all. I can log in internally and everything is ok, but from the outside, I get the traditional login box, even though I am using https, and I either get "Page cannot be displayed", or I get in, but I get a message saying that I do not have permission to open the mailbox.
HELP!!!!!!!!!!!
By the way, my setup is a clean install of 2003 Server R2, with Exchange 2007 32-bit on the same server. I'm hoping it's not a 32-bit issue. I am working on a 64-bit system now.
Ken
< Message edited by kenjancef -- 17.Jan.2007 3:27:06 PM >
I gave up with ISA 2006, and reverted to ISA 2000. I followed the tutorial for seting up Exchange 2003 OWA on ISA 2000 and it worked. I had some IP connectivity problems at first. Duplicate IPs on the Public addresses!
Troubleshooting this is really difficult. If you are not using ISA, you have to look up on what you are using as a firewall how it can do SSL tunnelling. Because that is what you need to do. Pain the petuki.