chrisl Posted January 2, 2008 Posted January 2, 2008 Hi,We've had this problem for a while now. We have a workaround (I'll explain later) but I'd really like to get this fixed. When we log into OWA on our W2003SBS Exchange 2003 using internet explorer, we see this:Instead of the nice interface, we end up with this mess. It used to work a long ways back, and we're not really sure what changed to cause this. We've been able to get around it by using firefox (which defaults to the "old OWA interface") but we'd like to get back to the nice interface we used to see in IE. Does anyone have any suggestions? We've uninstalled and reinstalled the OS with no change.
chrisl Posted January 2, 2008 Author Posted January 2, 2008 also, we only see this screen on other computers. I can load the correct looking website on the server itself in internet explorer.
chrisl Posted January 2, 2008 Author Posted January 2, 2008 Can you re-link that image?I can load it on a different server, yes. In the mean time, I can see the buttons (all look strange, but they work), but the majority of the page is white, and it says loading in the main viewport instead of mail messages. give me a minute or two to re-host.
chrisl Posted January 2, 2008 Author Posted January 2, 2008 (edited) Does that work better? Edited January 2, 2008 by chrisl
cluberti Posted January 3, 2008 Posted January 3, 2008 Much better. I've seen that happen before when I disabled scripting in the browser - this will not be a client-side problem.What happens if you build a box from scratch (not on the domain or getting your policies applied) and visit the page?
chrisl Posted January 3, 2008 Author Posted January 3, 2008 I don't know if that's going to be something I can check. We're a small company (6 people) and this is our only server. We only have client computers laying around aside from this one server. I've been checking in my browser on the client side. I haven't found anything blatantly blocking scripts yet (I'll keep checking). on the client side, it doesn't seem to matter if we're running IE6 or IE7. We're running IE6 on the server. Is there a particular port that needs to be forwarded to the server to insure scripts get sent, or does it all work on port 80?
chrisl Posted January 3, 2008 Author Posted January 3, 2008 I also turned on the messages for debugging in IE7 on my client. I see this message come up after a couple minutes:Problems with this Web pag might prevent it from being displayed properly or functioning properly. Line: 538Char: 1Error: Class not registeredCode: 0URL: <our web address>/Exchange/clafleur/?Cmd=navbarany idea what this might be?
cluberti Posted January 3, 2008 Posted January 3, 2008 Well, another question would be, are the clients all on the same network as the SBS server, or are you hitting this over the internet? The fact that all clients have the issue but not the server would indicate some sort of server-side or network issue, but are the clients connecting to OWA from the same network?
chrisl Posted January 4, 2008 Author Posted January 4, 2008 The server itself does not have the problem. Clients on the same network as the server do have the problem. Clients over the internet do have the problem.
cluberti Posted January 5, 2008 Posted January 5, 2008 Since this is an SBS server, if you completely disable the firewall on the server, do internal clients display the web page properly?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now