exchange admin's

Verge

Supreme [H]ardness
Joined
May 27, 2001
Messages
7,819
Anybody here mess with exchange 03 very much, having a problem with our webaccess and i need somebody to look at a nice screenshot of what it's doing... i'm clueless as to how to fix it
 
exchange 03
outlook web access
frontend server pointing to email server
IIS 6.0

i get this after i login

webmail.jpg





if connected to the internal network, i can login fine by going to //server/exchange, just not from the outside
 
Everyone gets that or just you?

Cleared your browser cache?


all accounts



ok, just fired up the old email server, moved some accounts over, webmail works fine on it... accounts on the new server, pull up the jumpled page.. shouldn't the frontend server automatically direct users logging in to the proper server ? All the settings i can find are the same on both, but one works now, and one doesnt :(
 
permissions on the IIS folders?
I had that same problem before and I believe I uninstalled IIS and reinstalled it to correct the problem
 
I had that problem on one server.

I forget exactly where the setting is, but check the properties (IIS) on the default site and look at the IP restrictions. It may be limited to your local subnet which is why it works internally. It's blocking the page graphics.

When I found that, I shook my head, "No friggin' wonder it ain't workin' right!" :)

I have no idea how it gets setup that way. OWA serves no purpose if you can't get to it from outside the local subnet. I think it must be some security wizard/setting someplace that borks this up.

Your screenshot has the buttons though. When I had that problem, very little was displayed, the buttons were all those little red "X" placeholders. Worth checking anyway though. The only difference between internal and external is the IP address range. In your case, it almost looks like the graphics are there, it's just the Exchange data that's missing. Check the same thing in Exchange, make sure that authenticated users have access regardless of IP address. Change one thing at a time that looks like it may be related. Test the new setting and if that doesn't fix it, put it back the way it was. :)
 
Make sure all Exchange boxes are on the same service pack. There is a kb article about that somewhere on MS site.

Try searching for OWA "loading..."
 
This is the reason why, in the best practices manual, they state to upgrade all FE 1st, and then the BE.
 
I was having the same issue with my exchange servers, seemingly at random with users.


I ended up going SSL w/FBA and it stopped, and made the users happier (a custom company login screen with fancy colors makes end users happy)
 
I was having the same issue with my exchange servers, seemingly at random with users.


I ended up going SSL w/FBA and it stopped, and made the users happier (a custom company login screen with fancy colors makes end users happy)

Funny on my 2003 server I had to disable FBA because the damn IIS would keep erroring the end user that the server was too busy! Silly thing there was only one person trying to connect with OWA at the time and it was too busy! LOL
 
Back
Top