It's been a while since I've used Experts Exchange but I remember a time when answers were provided rather than links to links which vaguely apply. Oh well, times change and perhaps I need to catch up.
Checking the ports was the right answer. If you're having this problem don't bother with the links, check your ports.
I went ahead and bit the bullet and called MS support to see how to do this, so for those of you who want to know and want to save the $259, here ya go:
Open IIS.
Expand your Sites.
Right-click the Default site (which OWA uses), select Edit Bindings - note the IP addresses and the ports being used.
Right-click the Sharepoint site, select Edit Bindings - note the IP addresses and the ports being used.
If they are using the same IP / Port combo you're going to have the problem. (Duh...I just couldn't find the friggin' Edit Bindings.)
So what I ended up doing is Editing the Bindings so that Sharepoint uses the internal IP address on port 80 and Exchange / OWA uses the external (firewall) address on port 80. This gives a unqiue IP / Port config for each of the sites. It also eliminates the ability to use the webmail function internally (unless you go to the Exchange server's external IP address), but that's what Outlook is for, right?
So, I hope that helps.
bvinson
Main Topics
Browse All Topics
by: Exchange_GeekPosted on 2008-11-18 at 18:29:56ID: 22991024
Check which ports Sharepoint and Exchange Virtual directories are trying to work - this might give you some thing to think about.
Ref:
http://www.exper