We are running Windows 2000 Advanced Server (SP3) with Exchange 2003 Enterprise Server
We have two information stores, "Employees" and "Non-Employees"
We have an OU for each one of those stores. (Ex. Employees, Non-Employees)
A current user or created user within the Employees OU with a mailbox in the Employees store can login to outlook and OWA without any issues or problems
We have created 5 new users within the non-employees OU and mailboxes within the Non-Employees store
These users' mailboxes didnt show up within the Non-Employees store even after several minutes and running recipient update services within exchange and domain replication.
We created a global group with the 5 users in it and created a recipient policy in exchange to set a new primary SMTP address for their email.
We attempted several times with each account to setup outlook profiles in which the exchange server could not resolve their names. We had proper crendentials and connectivity but because the mailboxes were not showing up in the store we couldnt resolve their names.
We then tried logging into OWA with these accounts and were able to. We tried this with two accounts. After that we saw that the mailbox was in the store and shows the last logon from our OWA connection. We then did this for each account.
After this we attempted to setup the outlook profiles once again and still had same issue. All mailboxes were in the store and proper crendentials and connectivity was being used but still couldnt resolve names.
We then tried logging back onto OWA, we put in correct user and password but we could not login. We were prompted 4 times before the UNAUTHORIZED webpage for OWA came up. Oddly enough, clicking refresh we were able to get into the mailbox. We were able to send and receive and change account options and even change password.
We need these users to be able to successfully login to OWA as well as outlook without any complications. These users are remote and have proper access in. We do not want POP3 coming into our server so OWA needs to work for them flawlessly.
We also need to be able to login locally to outlook so we can import contacts and PSTs for these users who are currently using a different SMTP server.
What needs to happen to ensure this problem gets fixed for these users and future users we create in the same manner?
What is the root cause of this and how can we fix it for good?