We run Exchange in a demo environment in which its loaded on the same server as a couple additional web applications. Because of this, we have several IIS web sites - the Default Web Site being the one thats used exclusively for IIS. To access each of these sites, we have all of the sites using specific host headers for each. The problem Im running into is that Exchange seems to have an issue with having a host header defined as an IIS binding. Up to this point, the only issue I had noticed was we have been unable to access the Exchange Mgmt Console, but everything else - OWA, Outlook, SMTP relaying - all worked without an issue. Well, we just ran into another piece that seems to "break" when specifying a host header - the Exchange Web Services. We were pulling our hair out in determining why one of our web apps that use EWS wasnt working and sure enough, once I removed the host header, it worked without issue. Has anyone had any luck using host header bindings? Is there some special configuration thats required to make this work? Thanks.

What version of Exchange? What issues are you have with EWS? There is a known issue with Exchange 2010 SP1. In SP1 EWS is being used for more often in OWA. When a host header is configured then some functions in OWA break, such as deleting mail, marking read\unread items, etc. On the IIS site that is being used for Exchange, instead of using a host header, maybe you can use different port number for HTTP and on HTTPS you can still use port 443.MCITP: Enterprise Messaging Administrator 2007/2010 | MCITP: Server Administrator | MCTS: Windows Server 2008 Applications Infrastructure, Configuring | MCP | MCDST