Hello, I have run into an unusual problem (in my experience) where I have an Exchange 2003 org, with 2 Front-end servers and several backend servers. I have added 4 new (VMWare) Exchange 2003 SP2 servers to the site, and 2 of them are fully functional, except for users on them are NOT able to access OWA via the front-end servers. I found this (My mailbox being part of the test) by trying to access OWA from home. No VPN but simply connecting to the ISA server. Now I know this worked before I moved my mailbox to the new servers, but sense I simply receive a logon prompt again or from outside I receive the error that I could not be logged on and to verify my account. It’s always been my experience that once you add new backend servers, the front end will simply know of their existence being in the Exchange organization, and offer up OWA without any further changes. I seem to be missing some step here, but not sure what it is. Any help would be appreciated!

First rule out ISA by trying to connect via the front-end servers inside your network.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Yes, I did try that, sorry I didn't include that part. when I try to connect directly from the frontend servers I get the same responce.

Primary reason is a version mis-match. The backend server is higher or different patch level to the frontend servers. The frontend servers should always be the highest version of the two. The quick and dirty method to check is through the \exchweb virtual directory. Check the version numbers listed. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Try logging on via OWA directly to the mailbox server. Make sure that the mailbox server does not require SSL. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

That works. I have also tried logging on from other backend servers and it works there as well.

With HTTP as opposed to HTTPS?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

When I use HTTPS I get the OWA logon page, and the result is "you could not be logged on, make sure your username is correct" using only HTTP I simply get the logon window over and over. This being from both front end servers. On all back end servers both methods work fine. (Thanks for your help Ed! really you rock!)

HTTP doesn't redirect to HTTPS on the back-end server does it? You don't have forms-based authentication enabled on the mailbox servers, do you? Check the authentication methods between the working and non-working mailbox servers and see if you notice any differences. Also, take a look at the IIS logs on both the front-end and mailbox servers and see if there is anything helpful there. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hello Ed, sorry for the laps.. I took your advice and did a side by side comparison of each setting for servers working and those not. Checking the virtual server config under HTTP. in all cases the Forms based authentication is unselected. I did find that on the Front-end servers it was, but I expected that. Still all back-end servers are NOT set for this. I spent time reviewing the IIS logs on both Front-End servers and they likewise didn't reveal much except a 401 5 0 at the end of the string. Research on this was limited but I found a few others having similar issues http://www.exchangeserverhelp.com/ftopic20532.html http://forums.msexchange.org/m_1800427632/mpage_1/key_/tm.htm#1800427632 however my Exchange servers are not on a cluster and they are all Windows 2003 SP2 Exchange 2003 SP2. So I'm not sure this applies as these address issues on Windows SP1, but reviewing SP2 this particular KB isn't listed. I'm considering a call to Premier support as a next step. Thanks again for your help!

Running or swimming laps? Exercise can be good for the brain, I guess. Please verify the following: Mailbox servers don't have the "This is a front-end server" checkbox selected. Reboot both the mailbox and front-end servers and see if that fixes things. The new mailbox servers are in the same administrative group as the front-end servers. The new mailbox servers are on the same Exchange version and service pack as the working ones. Users have a valid SMTP address. You can log on directly to the back-end server using HTTP, not HTTPS. The Default Web Site and virtual direcotries underneath are not configured to require SSL. Please post the entire entries from the IIS logs from both the front-end and mailbox servers if none of these suggestions help. A Premier Support call isn't a bad idea if you don't have the time to kill here.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Ok, after further research I learned the Front-end servers here (2 of them) were in an NLB. Additionally there are two more Front-end servers in another Location that I was informed about and when I used them I was able to access mailboxes via OWA. This led me to believe the new servers were Ok, and so.. Duu.. Rebooting the Front-end's I had been using solved this problem. Feeling a bit embarressed, but once again, thanks Ed! When in doubt, reboot!