[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 226
  • Last Modified:

OWA users cannot authenticate internally or externally

OK - so I know there are lots of questions already asked like this but I am stuck.  The situataion is this.  We have a completely new setup with our servers.  Now running VMware boxes - one for AD, one for Exchange, one for File & Print and a fourth for admin tasks.  All but the admin tasks are Server 2003.  The users, OU, data etc. were transferred from a SBS2003 box.  We have a checkpoint firewall server.
I cannot get OWA working and support from the installers is delayed - not their fault its a timezone thing.  Anyway, I can get to the logon screen both internall using the IP and externally using fdqn or IP.  In either case when I try to logon I get the username/ password message is incorrect.  I have worked through both these articles and looking for advise on where to go next.  
http://support.microsoft.com/kb/301428 
http://support.microsoft.com/kb/327843 

and we were getting these error message until the exchange box was rebooted http://support.microsoft.com/kb/271335
now event log looks OK.  

I only have limited permissions on my account so may not be able to access all that is required but need to try anyway.
0
Jenny Coulthard
Asked:
Jenny Coulthard
  • 3
  • 2
1 Solution
 
ZephyrTCCommented:
Are you getting any error messages when you log in or just getting the bad username and password?

Have you tried putting the domain name before your username?
Example: Domain\user

If the server wasn't configured properly, you will need to do this in order to acess OWA.

Also, I would suggest adding a CNAME (Alias) to your DNS structure internally to point your FQN to your internal mail server IP Address.  this will allow your users to only remember 1 name for their OWA access needs.
0
 
Jenny CoulthardIT ManagerAuthor Commented:
- I am not getting any error messages - just bad username or password.
- I have tried putting the domain\user and user same result.
- will look at addin a CNAME but I dont know if that will solve my problem
Regards,
0
 
Deepu ChowdaryCommented:
Hello purbrick
Check certificate once.. if everything is good, try with another username and password..
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Jenny CoulthardIT ManagerAuthor Commented:
Hi - I checked the certificates - there is one which covers the domain which is good.  There is another which has teh exchange box name, this is not trusted.
I have tried many username/password combinations
0
 
Deepu ChowdaryCommented:
Try adding the certificate to trustedroot..

Try this once :

http://support.microsoft.com/kb/327843.

Hope this will work..
0
 
Jenny CoulthardIT ManagerAuthor Commented:
apparently there was something wrong with the VPN settings, everything else was OK.
Thanks anyway.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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