SBS 2003 SP2

I am having an issue with OWA. When you hit the URL it prompts for a login you enter the credentials and it just opens a blank page. So it looks like a successful login it just doesnt open your mailbox. I cant find anything in the event log other than a successful login.

This started after I was trying to fix a permissions issue and the recommendation was to remove the IIS directories and let exchange rebuild them. At first I thought it was the restricted IP address error but I went into exchweb and granted every IP access and that didnt fix it.

Any ideas would be appreciated

If I were you, I'd log into a working SBS 2003 Server and do a vdir-by-vdir comparison of the auth settings and configs.

By default the ExchWeb vdir has Granted as the selected option and the field beneath it is unpopulated. Anonymous access should be enabled and no other auth options selected. SSL should be required.

 

Dave Shackelford
ThirdTier.net

I dont have another sbs server

I do have it as granted and anonymous is enabled

Make sure your settings are as follows:

The Exchange vdir should only allow Basic auth and disallow Anonymous. It should grant access to all IPs. It should require SSL.

The ExAdmin directory should only allow Integrated Auth and disallow Anonymous. It should grant access to all IPs. It should require SSL.

The Exchange-OMA directory should allow Integrated and Basic Auth and disallow Anonymous. Only the local server IP (and the loopback IP) should be allowed access. SSL should not be required.

Do you know if you have Forms Based Authentication enabled in the Exchange System Manager? Under Protocols -> HTTP?

Dave Shackelford
ThirdTier.net

Will it work without SSL in order to test it? Then i could add SSL after it actually works? I just didnt want to add another layer to the issue with SSL until it actually worked and then i was thinking i would go ack and turn on SSL

I wouldn't think about it that way. If you just follow the defaults that I laid out, SSL settings shouldn't get in the way of anything. Plus, it's not SSL that's the problem, it's probably the auth mechanism you are using to get from IIS to the actual Exchange database.

Dave Shackelford
ThirdTier.net

Forms based auth is not enabled and I have matched these settings and still does the same thing