No host headers and no OMA (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Outlook Web Access



Message

SUSANVV -> No host headers and no OMA (14.Apr.2006 6:35:19 PM)

In the IIS configuration for the Default Virtual directory there are no host headers and no actual IP address. For Multiple sites the port 80 is Default and port 80 with no host header and the secure is Default and port 443. We cannot get OMA working nor Public Folders accessed from the web. Could this be part of the problem? I am thinking of adding the server IP address and our server name to both sections. Should I also add our static IP address that points to the Exchange server for mail?

Also can I restart the IIS service without affecting users logged on who are using Outlook 2000?

TIA for any help.

Sue Van



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 7:56:07 PM)

Hello again Susan V V.

Leaving the IP address as 'All Unassigned' is usually best, as is leaving the host header empty.  Do you have SSL required on your Exchange VDir?  That causes problems for OMA.



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 7:56:52 PM)

Oh, and restarting IIS will not affect your Outlook users.



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 8:26:05 PM)

Hi Leederbyshire,
Thanks again for your help. Yes, we do have SSL, a Thawte certificate. OWA and OMA will be accessed mostly from the Internet. I saw the information at Microsoft about creating an Exchange-oma directory because of the SSL problems. I first tried configuring the default OMA directory exactly the same, including the registry setting (referencing \OMA instead of \exchange-oma) but that didn't help. I plan to try the exchange-oma fix this weekend. Thanks to your help, we now have OWA working except for Public Folders (another question on this forum).

Thanks for your answer regarding restarting IIS. I may try the exchange-oma this afternoon.

Please check out my Public folders problem also.

Thanks again.

Sue Van




leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 8:31:12 PM)

One thing you might do is to not require SSL on the Exchange VDir, but only open port 443 to the Internet on your router.  That way, your users can only access OWA using SSL (because only port 443 is open), but OMA can access Exchange internally on port 80.  The only problem with this would be that you may have other Web content, besides OWA, available to the Internet, and this would no longer be avaliable if you closed port 80.



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 8:42:52 PM)

I think part of our problem is that we want people to access Exchange remotely using the new cell phones or blackberrys, as well as with Internet Explorer. Could they still access their email using https also from their phones?

Thanks again.

Sue Van



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 8:46:32 PM)

Usually, yes, but you will need to try it to make sure.  Some mobile ISPs use proxy servers that do not support SSL connections.



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 8:54:16 PM)

So basically I just remove the SSL requirement from the Default web site in IIS. The transmission will still use the SSL because of port 443. If this is true, why would you need to require SSL? Would that be if you had port 80 open but wanted to have a secure channel? We are going to be creating other virtual web sites in the future. Would we just put them on a different port and require SSL on them? Have I got it right? I am asking questions because my boss is going to want to know.

Thanks again.

Sue Van



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 9:01:09 PM)

When you apply a cert to a Web server, you can then use http or https to access any Web directory.  When you select the checkbox that says require SSL, then that stops you accessing it using plain http.  But if you leave the requirement unchecked, but close port 80 at the router, then that kind of has the same effect for external users (internal users could still use http, though).  They do not get any response at all from the Web server using http because they can't even reach it.  If port 80 and 443 were both open, and you checked the 'SSL required' tickbox, then they would get a response from the server, but only to tell them that they need to use https.



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 9:27:48 PM)

I assume after each change I should restart the IIS services? I removed the requirement for SSL from the default web site. I did not apply it to the child folders-it was already not required for OMA. It did change what was displayed for a logon for OMA. I am logging on OK but I just can't see the OMA site. I get the error message that a system error has occurred.

Thanks again.

sue



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 9:31:29 PM)

You wouldn't normally need to restart IIS to apply the SSL changes.  But, if OMA is already confused by a previous SSL problem, you may need to restart the IIS Admin service (not just IIS).  There are lots of system error associated with OMA.  Try Googling for the exact error message that you see.



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 9:40:57 PM)

Our OWA for our mailboxes works and I have to confess I am concerned about screwing that up. Is there anything in particular that I should NOT do so as not to destroy our OWA?

Thanks.
Sue



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 9:47:57 PM)

Very hard to say. OWA is normally quite resilient; but on the other hand, you hear of so many broken installations that you have to wonder what's going on out there.  The obvious answer is not to tinker with permissions on VDir, folders, OUs and system accounts that you don't recognize, because very often the symptoms don't appear until a few weeks after.



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 9:56:21 PM)

Thanks for all your help. I will keep you posted after I try a few things. Right now I am only messing with the default OMA directory. The only other thing I may try is the Microsoft fix with the exchange-oma directory. I saw some out there that said that worked but configuring the default OMA directory did not.

Thanks again.

Sue




SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 10:09:08 PM)

Should the local path for the OMA directory be set to c:\program files\  etc or should it be set to \\.\backofficestorage  etc? I saw something elsewhere that has that path set to backofficestorage.
There doesn't sseem to be anything anywhere that emunerates exactly what some of these things should be.

Thanks again.

Sue



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 10:16:05 PM)

The OMA VDir has special properties that mean you can't create it yourself in IIS Manager.  Why do you need to create it again - has it been deleted?  If you do need to recreate it, use this (but ignore the part about deleting Exchange and Exchweb, just let it create what's already missing):

http://support.microsoft.com/?kbid=883380



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 10:21:22 PM)

No I still have the default OMA directory. That was one fix from the Microsoft site. KB 817379. I don't understand why you would need it either but that was the articles recommendation to keep SSL everywhere else.

I removed the Windows Integrated Access and now I get an error that the Item no longer exists. I may put it back as at least the error message then had more information.

Thanks.

sue



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 10:24:39 PM)

I thought of something esle that I have been reading. Our primary SMTP address is different from our internal address--one is .local and the primary is .com. Could this be interferring at all?

Sue



leederbyshire -> RE: No host headers and no OMA (14.Apr.2006 10:35:30 PM)

Oh, right - 817379 .  When you were asking about the path for the OMA VDir, I thought you were trying create an OMA VDir.  That article is used to create an extra Exchange VDir for use with OMA, so I see what you mean now.  But you shouldn't need to enter the path yourself - the method described (exporting the XML file, and importing it again) takes care of all the VDir properties except the name, which needs to be changed.

Your users should all have an email address in the Primary domain.  It doesn't have to be their default address, but it does need to be in their list of addresses.



SUSANVV -> RE: No host headers and no OMA (14.Apr.2006 10:41:00 PM)

We do have both. I know it should have the right directory for OMA however, I you right click on OMA in IIS and select Properties. On the Virtual Directory page, in the Local Path box, the path leads to CL\Program Files\Exchsrvr\OMA\Browse. Is this where it belongs? The Exchange directory's local path is \\.\backofficestorage\domain name.com\MBX. Is this correct for OMA instead of a \\.\backofficestorage directory.

Thanks again.

Sue



Page: [1] 2 3   next >   >>